Document release process for Crossplane extensions. #913
Conversation
Signed-off-by: Jason Tang <[email protected]>
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Jason Tang <[email protected]>
jastang
force-pushed
the
785-extensions-release-process
branch
from
69668fc to
5e5345b
Compare
There was a problem hiding this comment.
This is a great start @jastang, thank you for stepping up to take on a long annoying gap in the community's knowledge base! 🙇♂️
I think we're still missing some high level and general information for folks that aren't ready to see the details of pipeline steps. Could you consider adding two IMO important focus areas to this guide?
- A high level general outline of what an extension release is, how the parts all fit together
- A practical set of steps that they follow to release their extension. This will probably be THE most useful and popular section of this guide. People would hopefully be able to come to this list and mostly follow it without thinking too much 😉
|
|
||
| {{< hint "note" >}} | ||
| Some custom workflows may accept an explicit input for the remote reference, | ||
| which overrides inferring from a git ref or tag. The [`ci.yml`] file for |
There was a problem hiding this comment.
this ci.yml link is not resolving/rendering on the preview site, e.g. in https://deploy-preview-913--crossplane.netlify.app/v2.0-preview/guides/extensions-release-process/#branching-conventions
|
|
||
| ### Configure target registry | ||
|
|
||
| The provider template repository includes a top-level `Makefile`. Edit |
There was a problem hiding this comment.
a link to the makefile or at least the provider template repo here would be very helpful
Adds a new Guide detailing the conventional release process with GitHub Actions for Crossplane extensions.
Fixes #785