workflows: Use gh command line to create issues
#1116
Conversation
gh command line to create issues
|
Here's the change in action: anoopcs9#1 |
|
Should we add the additional complexity to check for any existing issues with the same title? |
No, I think it would be unnecessary given how infrequently we run the action. If it starts to be annoying in the future we can revisit that then. |
af559ab to
855db3e
Compare
|
It took me sometime to realize the complexity with handling multiline strings while storing information in GitHub actions which I finally avoided by writing the necessary contents to a file as indicated in the docs. See anoopcs9#4 for a sample issue created with the current changes. An alternative is to retain the current logic in script to create a body.md with just the contents(without title) for the issue and calculate the next upcoming release version as a series of bash builtin commands. |
855db3e to
829e15d
Compare
This is done in preparation to make things easier for us to create github issues using `gh` command line. Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
With the third party github actions disabled we directly make use of `gh` command line to create a bare minimum GitHub issue for any API updates to be performed in the next upcoming release. Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
829e15d to
ecdbc58
Compare
With the third party github actions disabled we directly make use of
ghcommand line to create a bare minimum GitHub issue for any API updates to be performed in the next upcoming release.