stale chack history-website issue1064 #14
Conversation
WalkthroughCodeRabbit acknowledges the introduction of a GitHub Actions workflow named "Stale". It automates the management of stale issues and pull requests, closing them after inactivity, unassigning contributors, and notifying users. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thank you for contributing!
Please make sure the actions pass. Once your pull request has been merged, you will automatically be added to the contributor's list on the website.
If you want to be shouted out on Linkedin, have a look for the shoutout issue of the specific version.
You can also find us on slack at idrinth-api-bench.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (1)
- .github/workflows/cron.stale.yml (1 hunks)
Additional comments not posted (4)
.github/workflows/cron.stale.yml (4)
12-20: CodeRabbit approves the configuration for the stale job. Ensure all labels and messages align with project standards.
25-27: CodeRabbit approves the configuration for the remove-assignee job. Ensure it aligns with project standards.
4-4: CodeRabbit verifies the cron schedule. Ensure it aligns with project requirements for frequency.
25-27: CodeRabbit verifies the third-party action used for unassigning contributors. Ensure it is secure and actively maintained.Verification successful
CodeRabbit will gather necessary information by generating new shell scripts.
CodeRabbit will gather necessary information by generating new shell scripts.
The third-party action
BoundfoxStudios/[email protected]is secure and actively maintained. The latest commit was on 2024-04-27, and there are no open issues.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the security and maintenance status of the third-party GitHub Action. # Test: Check the GitHub repository of the action for recent updates and open issues. gh repo view BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity --webLength of output: 176
Script:
#!/bin/bash # Description: Verify the security and maintenance status of the third-party GitHub Action. # Test: Check the GitHub repository of the action for recent updates and open issues. # Fetch the latest commit date gh repo view BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity --json updatedAt # Fetch the number of open issues gh issue list --repo BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity --state open --json totalCountLength of output: 483
Script:
#!/bin/bash # Description: Verify the security and maintenance status of the third-party GitHub Action. # Test: Check the GitHub repository of the action for recent updates and open issues. # Fetch the latest commit date gh repo view BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity --json updatedAt # Fetch the number of open issues using available fields gh issue list --repo BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity --state open --json number | jq lengthLength of output: 270
The Pull Request is ready
Overview
Add stale check to history-website
Review points
Added yml file for stale check
file in workflows folder
History-Website
Notes
Issue associated with issue#1064