[#1166] Set up GitHub Actions#1168
Conversation
|
@damithc Need your review on this. I have kept it at 30 days for now before declaring it stale and 7 more days before closing it. |
| with: | ||
| repo-token: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| pr-message: 'Thank you for submitting this PR. Please double-check to ensure that you have followed our contribution guidelines and update the commit message and title of your Pull Request accordingly. Once you are ready, and all the checks pass, do let us know!' |
There was a problem hiding this comment.
is it possible to add the link to contribution guideline here?
There was a problem hiding this comment.
Apparently they don't allow links as of now. We might have to proceed ahead with the link functionality for now.
There was a problem hiding this comment.
Did you try with Markdown? i.e. [text](url)
| DAYS_BEFORE_CLOSE: 7 | ||
| STALE_ISSUE_LABEL: 'stale' | ||
| STALE_PR_LABEL: 'stale' | ||
| STALE_PR_MESSAGE: 'Hi, were are going to mark this PR as stale because it has not had any updates for 30 days. If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.If you are still working on this PR, please make a follow-up commit within 7 days and do leave a comment if you are still working on this PR. Please also let us know if you are stuck so we can help you!' |
There was a problem hiding this comment.
we are going to
inactivity for 30 days?
If you are still working on this PR, please make a follow-up commit within next 7 days and leave a comment to remove the stale label.
|
@damithc There is an update on this. The action also closes issues. And there is only one way to stop it rn. By using the |
will that prevent PRs from closing too (if the same label is applied)? |
No, it won't. Only the issues. UPDATE: Found another way to handle this. Shouldn't be a problem anymore |
If it's not a limitation of GitHub's API, then we can fork and upgrade the project. |
| - name: stale | ||
| uses: gatsbyjs/stale@v1.1.0 | ||
| with: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Will this work for forked PRs as well?
There was a problem hiding this comment.
Should work I believe. I have tried it on one of my repos from another account.
There was a problem hiding this comment.
Do u mean this repo? It seems like the labelling is working, but the closing is not tho.
One of the PRs was created 5 days ago, but according to ur yml file, the closing is one day after the PR is marked as stale.
Don't think it a GitHub API limitation, since other actions provide the same feature. I will look into it in another PR? Cause will take a bit of time to figure that out. |
| on: | ||
| schedule: | ||
| # Runs at 00:00 every day | ||
| - cron: '0 0 * * *' |
There was a problem hiding this comment.
A clarification: does this check run every day?
|
This PR will take a bit of time. Creating own action based on our needs after forking. |
|
Update: Have gotten it to work for labelling and closing PRs. If any suggestions on how to remove the label after a update, do let me know. |
Perhaps can look at this? https://developer.github.com/v3/issues/#update-an-issue |
Thanks! Looking into it. |
|
The update for removing the label is on its way. Shall we wait or proceed for once? For the first 1/2 months, we might have to remove the labels manually but then shall get automated. |
|
Hi, Can I know the status of this PR? the change part seems to be weird? |
|
Continued in PR #1299 |
Fixes #1166