feat: add issue-body default - #47
Conversation
lemeurherve
commented
Oct 20, 2022
Does this mean |
joshjohanning
commented
Oct 20, 2022
Nice, yeah @lemeurherve - I updated the readme accordingly. @gr2m / @stefanbuck , take a look at the readme and see if that's how you want it presented. |
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Hervé Le Meur <91831478+lemeurherve@users.noreply.github.com>
| template-path: .github/ISSUE_TEMPLATE/bug-report.yml | ||
| ``` | ||
| The text to be parsed can be set explicitly using `issue-body` input, otherwise it can be left to use the default value of `${{ github.event.issue.body }}`. |
There was a problem hiding this comment.
@lemeurherve@gr2m , what do we think about this line?
I originally wrote it longer, but cut it down for brevity, and people don't really need to see the historical references here?
Originally wrote:
In version 3.0.0, new input for
issue-bodyis added to mitigate script injection attacks (see: #42). Version 3.0.1 defaultedissue-bodyto${{ github.event.issue.body }}for convenience (see: #47). The text to be parsed can be set explicitly usingissue-bodyinput, otherwise it can be left to use the default value.
There was a problem hiding this comment.
I'd say it's great, we can iterate on it later, I'd get this PR merged
stefanbuck
commented
Oct 20, 2022
Amazing! It's really awesome to see you all to care enough about this little project to spend your time improving it. Thank you ❤️ |
For some odd reason the release pipeline was using an older commit as a baseline and this resulted in another 3.0.0 release ergo the pipeline failed with |
stefanbuck
commented
Oct 20, 2022
gr2m
commented
Oct 21, 2022
I had a quick glance but don't know what the reason might be. I gotta go for today, but could you file an issue and assign it to me please? I'll have a look tomorrow |
joshjohanning
commented
Oct 25, 2022
I had this browser tab still open for some reason, so I created the issue 👌 ☝️ |
closes#46
🎉