Mitchell Simoens

I too would be open to maintaining a fork. We need a separate account for it as I don't like these things to be bound to individual accounts and we...

@cabello I did setup a Github [org](https://github.com/GraphiDocsOrg/) and [repo](https://github.com/GraphiDocsOrg/docs). lmk if you want to be added. Need to do some cleanup before publish to npm but I did create a...

@carldunham yea, I stopped because I went in thinking I wasn’t going to be the only one maintaining and turned out I was being only one so when the project...

@eallik drop it. Yes it does say the issue was closed by Bucs. I am aware of it because Bucs brought it to my attention but working for Sencha means...

I wouldn't say it's a done deal, I'm just gonna push for it :) The core devs are a lot smarter than me so issues like this won't be a...

Whoa, I almost hit the 'Comment & Close' button :)

This shouldn't be needed as [here in the code](https://github.com/ModusCreateOrg/gimbal/blob/master/packages/gimbal/src/config/index.ts#L65), we look for the config file. The glob that is used is `.gimbalrc.{js,json,yaml,yml}` and it's using the cwd which defaults to...

@bronz3beard the entrypoint of the gimbal action is `gimbal` which means you can use a step's `with` to add additional args: https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswith

We will need to copy in a couple files like the license and readme like they do in this [Dockerfile](https://github.com/actions/heroku/blob/master/Dockerfile#L12).

I also think we need to look at how we are going to publish the action. Right now, we are saying to use `uses: ModusCreateOrg/gimbal/action@master` which will always use latest...