-
Notifications
You must be signed in to change notification settings - Fork 156
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' into fix/strpos-warning
- Loading branch information
Showing
12 changed files
with
130 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,6 +10,7 @@ | |
- [ ] Update this pull request's status from `draft` to `ready to merge`. | ||
- [ ] Review: Do a review of the commit to the `stable` branch to ensure the contents of the diffs are as expected. | ||
- [ ] Test: Check out the `stable` branch and test it locally to ensure everything works as expected. It is recommended that you rename the existing `distributor` directory and check out `stable` fresh because switching branches does not delete files. This can be done with `git clone --single-branch --branch stable [email protected]:10up/distributor.git` | ||
- [ ] Either perform a regression testing utilizing the available [Critical Flows](https://10up.github.io/Open-Source-Best-Practices/testing/#critical-flows) and Test Cases or if [end-to-end tests](https://10up.github.io/Open-Source-Best-Practices/testing/#e2e-testing) cover a significant portion of those Critical Flows then run e2e tests. Only proceed if everything tests successfully. | ||
- [ ] Release: Create a [new release](https://github.com/10up/distributor/releases/new), naming the tag and the release with the new version number, and **targeting the `stable` branch**. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the [closed issues on the milestone](https://github.com/10up/distributor/milestone/#?closed=1). The release should now appear under [releases](https://github.com/10up/distributor/releases). | ||
- [ ] Check release: Wait for the [Publish Release Action](https://github.com/10up/distributor/actions?query=workflow%3A%22Publish+Release%22) to complete, and then check the latest release to ensure that the ZIP has been attached as an asset. Download the ZIP and inspect the contents to be sure they match the contents of the `stable` branch. | ||
- [ ] Close milestone: Edit the [milestone](https://github.com/10up/distributor/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone. | ||
|
29 changes: 17 additions & 12 deletions
29
.github/workflows/no-response.yml → .github/workflows/close-stale-issues.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,30 +1,35 @@ | ||
name: No Response | ||
name: 'Close stale issues' | ||
|
||
# **What it does**: Closes issues where the original author doesn't respond to a request for information. | ||
# **Why we have it**: To remove the need for maintainers to remember to check back on issues periodically to see if contributors have responded. | ||
# **Who does it impact**: Everyone that works on docs or docs-internal. | ||
|
||
on: | ||
issue_comment: | ||
types: [created] | ||
schedule: | ||
# Schedule for five minutes after the hour, every hour | ||
- cron: '5 * * * *' | ||
# Schedule for every day at 1:30am UTC | ||
- cron: '30 1 * * *' | ||
|
||
permissions: | ||
issues: write | ||
|
||
jobs: | ||
noResponse: | ||
stale: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: lee-dohm/[email protected] | ||
- uses: actions/stale@v9 | ||
with: | ||
token: ${{ github.token }} | ||
daysUntilClose: 14 # Number of days of inactivity before an Issue is closed for lack of response | ||
responseRequiredLabel: "Reporter Feedback" # Label indicating that a response from the original author is required | ||
closeComment: > | ||
days-before-stale: 7 | ||
days-before-close: 7 | ||
stale-issue-message: > | ||
It has been 7 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 7 days, but if you have more information to add then please comment and the issue will stay open. | ||
close-issue-message: > | ||
This issue has been automatically closed because there has been no response | ||
to our request for more information. With only the | ||
information that is currently in the issue, we don't have enough information | ||
to take action. Please reach out if you have or find the answers we need so | ||
that we can investigate further. See [this blog post on bug reports and the | ||
importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/) | ||
for more information about the kind of information that may be helpful. | ||
stale-issue-label: 'stale' | ||
close-issue-reason: 'not_planned' | ||
any-of-labels: 'Reporter Feedback' | ||
remove-stale-when-updated: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.