search

GOG-Nebula / .github

0 stars 0 forks source link

Document build process #9

Open AndrewDWhite opened 2 years ago

AndrewDWhite commented 2 years ago

Document the build process to on board new developers faster and provide better visibility into the process.

urwrstkn8mare commented 2 years ago

Do you mean just the build process for the plugin or developing the plugin as a whole? If the latter, maybe should rename this to "Document development process"? Same as for the milestone label. BTW the build process falls under the developing process anyway.

AndrewDWhite commented 2 years ago

For this ticket, I mean documenting how plugins are built for deployment since our process may not be the same as the existing process friends of galaxy used. For example go into how plugins are built using automated workflows from manual review of pull requests and whatever process we use. It would make it easier for a new plugin developer to get their plugin reviewed and hooked into the process.

Documenting developing a plugin as a whole would be a different ticket if we plan to do that but at least we should provide links like the resources section of the galaxy plugins.

https://github.com/Mixaill/awesome-gog-galaxy

urwrstkn8mare commented 2 years ago

For example go into how plugins are built using automated workflows from manual review of pull requests and whatever process we use.

Oh I was under the impression that this was the developing process. But I think I get it now. Thanks

ABaumher commented 1 year ago

Not gonna lie, i really could use this. I have no idea how github build actions and such work. I've gotten the code to the point i can build and zip it using an invoke command and if gog uses that it'll work, but i have no idea how to automate that process.