Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sarif-support-for-code-scanning.md:runAutomationDetails fix #34820

Merged
merged 7 commits into from
Oct 17, 2024

Conversation

SwuduSusuwu
Copy link
Contributor

The previous example was "2021-02-01 == February 2, 2021" which is not normal calendar use. The new example fixes this.

Why:

Closes: #34819

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • [ X ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • [ X ] For content changes, I have completed the self-review checklist.

The previous example was "2021-02-01 == February 2, 2021" which is not normal calendar use.
The new example fixes this.
Copy link

welcome bot commented Oct 3, 2024

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 3, 2024
Copy link
Contributor

github-actions bot commented Oct 3, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team code security Content related to code security and removed triage Do not begin working on this issue until triaged by the team labels Oct 3, 2024
@nguyenalex836
Copy link
Contributor

@SwuduSusuwu Thank you for opening a PR! I believe this doc is following ISO date format, which should actually mean 2021-02-01 == February 1, 2021!

I'll get this triaged for review, just so another member of the team can confirm 💛

@nguyenalex836 nguyenalex836 added the waiting for review Issue/PR is waiting for a writer's review label Oct 3, 2024
subatoi
subatoi previously requested changes Oct 4, 2024
Copy link
Contributor

@subatoi subatoi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @SwuduSusuwu and thanks for raising a PR. You're right about the mistake.

Instead of just changing the written part to match the correct date, we should delete it altogether: different countries use different date systems and not everyone follows ISO8601, sadly. Stating the date doesn't add anything, either.

Once we resolve that point we can merge this on October 7th, after our freeze ends. Thank you!

| my-analysis/tool1/ | my-analysis/tool1 | None
| my-analysis for tool1 | None | my-analysis for tool1

* The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
* The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from January 2, 2022.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from January 2, 2022.
* The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1".

After calendar example, has "(note: this ISO8601 format is used in Europe + US, but your system locale can replace this)"
…m last commit

Removes trailing spaces from last commit
Partial reuse (removes ambigious language from this)
@subatoi
Copy link
Contributor

subatoi commented Oct 7, 2024

Hi, I appreciate what you're trying to say with the new changes, but we'd be better off keeping this simple and simply deleting the line I noted in my last suggestion.

@nguyenalex836
Copy link
Contributor

@SwuduSusuwu Hello! 👋 Just wanted to make sure you saw @subatoi's last comment. Once you've deleted the note that he referenced, we'll be happy to get his merged 💛

@nguyenalex836 nguyenalex836 added more-information-needed More information is needed to complete review and removed waiting for review Issue/PR is waiting for a writer's review labels Oct 10, 2024
@github-actions github-actions bot added the stale There is no recent activity on this issue or pull request label Oct 17, 2024
Copy link
Contributor

This PR has been automatically closed because there has been no response to to our request for more information from the original author. Please reach out if you have the information we requested, or open a new issue to describing your changes. Then we can begin the review process.

@github-actions github-actions bot closed this Oct 17, 2024
@nguyenalex836 nguyenalex836 reopened this Oct 17, 2024
@nguyenalex836 nguyenalex836 removed stale There is no recent activity on this issue or pull request more-information-needed More information is needed to complete review labels Oct 17, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 17, 2024
@nguyenalex836 nguyenalex836 dismissed subatoi’s stale review October 17, 2024 21:31

Applied suggestions in previous review

@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Oct 17, 2024
@nguyenalex836
Copy link
Contributor

@SwuduSusuwu I went ahead and removed the line noted in @subatoi's suggestion 💛 We'll go ahead and get this merged - thank you for raising a flag on this issue, and contributing to GitHub Docs! ✨

@nguyenalex836 nguyenalex836 removed the request for review from subatoi October 17, 2024 21:33
@nguyenalex836 nguyenalex836 added this pull request to the merge queue Oct 17, 2024
Merged via the queue into github:main with commit 776c8a9 Oct 17, 2024
44 checks passed
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code security Content related to code security content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sarif-support-for-code-scanning.md:runAutomationDetails fix calendar use
3 participants