Changed govulncheck to run on all source files (./...) instead of the built binary. This fixes uploading to GitHub Code Scanning as the location data will be valid, so it will get accepted.
After discussing changes with @bagtoad, we talked about consolidating the top-level readme further to reduce the amount of links.
Additionally, the Amazon Linux 2 and openSUSE/SUSE sections weren't contained appropriately in the official sections.
Now that our installation docs more clearly delineate official and unofficial installation methods, the maintainers are more open to contributions from communities.
These changes work to improve GitHub CLI users experience by bringing:
- clarity between official and unofficial installation methods
- insight into unofficial installation methods
- consistency across supported operating systems
Clarifies the triage process for bugs, enhancements, and docs issues, including the responsibilities of the first responder (FR). Expands and reorganizes label definitions, adds new labels for investigation and team triage, and updates the pull request assignment process to be load balanced. Improves instructions for engaging with issues and managing labels.
Fixes#11408
These changes enhance the GitHub CLI spam detection logic to automatically comment on and close suspected spam based on the past weeks of usage.
Additionally, there were a few minor enhancements to the script, allowing it to be executed from anywhere rather than the root of the local repository.
This commit makes a few notable changes:
1. Use the GitHub Actions automatic token for committing changes
2. Include workflow file in paths to trigger workflow
3. Checkout the default branch explicitly
* ci: improve spam detection evals
Signed-off-by: Babak K. Shandiz <babakks@github.com>
* ci: make test case names consistent
Signed-off-by: Babak K. Shandiz <babakks@github.com>
* ci: remove ill-indented/redundant test case
Signed-off-by: Babak K. Shandiz <babakks@github.com>
---------
Signed-off-by: Babak K. Shandiz <babakks@github.com>
This commit moves the `gh pr create` tab completion test closer to the logic rather than the commands that use it.
This should ensure that any command or flag that lists reviewers will present teams and users as expected.
This commit enhances the following scenarios to include organization teams as pull request reviewers:
1. Interactive `gh pr create` during additional metadata
2. Tab completing `gh pr create --reviewer`
3. Tab completing `gh pr edit --add-reviewer`
4. Tab completing `gh pr edit --remove-reviewer`
Additionally, a new `gh pr create` test case for ensuring that teams show up within interactive prompts has been added.
Introduces a new help topic explaining how to use exclusion qualifiers in GitHub search syntax with gh commands, including platform-specific instructions for Unix-like systems and PowerShell. Provides links to relevant documentation for further reference.
Co-Authored-By: Sid <41968447+sukhpreet-s@users.noreply.github.com>
