Felicity Chapman

Thanks for the reminder @jsoref When I searched for the text you quoted in the issue summary in http://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html, I failed to find it. Could you check that it's still...

@jsoref - many thanks for the clear reproduction steps. I'll tag this for an SME review.

Hi @jsoref 👋🏻 Apologies for the delay in getting back to you. I can confirm that there is no need to use Pascal case for the `reportingDescriptor name` property. The...

I didn't find it easily either. It's the last body parameter:

Interesting. That is the same link that I gave. I can certainly raise a request to look into the possibility of making more anchors available on the page. I suspect...

Thanks for your patience. It looks as if the article now includes the SME's explanation of how `help.text` and `help.markdown` behave: https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#reportingdescriptor-object. I suggest that we close this issue.

@christian-bromann - thanks for letting us know about this workflow problem. We're raising it with the product team.

@christian-bromann - thank you for your patience. I've been able to confirm how to sign the GitHub Marketplace Developer Agreement and will propose an update to the article to make...

I raised a pull request to clarify the behavior: - https://github.com/github/docs/pull/25778 You can see the proposed change in the [preview](https://docs-25778-ea4656.preview.ghdocs.com/en/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action) for that pull request.

👋🏻 @juliandunn We're reviewing all open help wanted issues as part of our preparation for Hacktoberfest next week. Sadly the link you provided to a simple example in https://github.com/github/docs/issues/17748#issuecomment-1151724407 was...