From 1db43a4ea6275c5ebf8026adeed929b0edb309e3 Mon Sep 17 00:00:00 2001 From: Darin Kotter Date: Thu, 1 Dec 2022 13:58:29 -0700 Subject: [PATCH 1/5] Update release template --- .github/release-pull-request-template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/release-pull-request-template.md b/.github/release-pull-request-template.md index dc4267c..32e6f6f 100644 --- a/.github/release-pull-request-template.md +++ b/.github/release-pull-request-template.md @@ -5,7 +5,7 @@ - [ ] Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the pull request), then merge `develop` into `stable` (`git checkout stable && git merge --no-ff develop`). - [ ] Push: Push your stable branch to GitHub (e.g. `git push origin stable`). - [ ] Release: Create a [new release](https://github.com/10up/action-wordpress-plugin-build-zip/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/action-wordpress-plugin-build-zip/milestones/#?closed=1). The release should now appear under [releases](https://github.com/10up/action-wordpress-plugin-build-zip/releases). -- [ ] Ensure the release [appears in the GitHub Marketplace](https://github.com/marketplace/actions/wordpress-plugin-build-release) correctly. -- [ ] Close milestone: Edit the [milestone](https://github.com/10up/action-wordpress-plugin-build-release/milestones/) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description field`), then close the milestone. +- [ ] Ensure the release [appears in the GitHub Marketplace](https://github.com/marketplace/actions/wordpress-plugin-build-zip) correctly. +- [ ] Close milestone: Edit the [milestone](https://github.com/10up/action-wordpress-plugin-build-zip/milestones/) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description field`), then close the milestone. - [ ] Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X.Y.Z+1`, `X.Y+- [ ]0`, `X+- [ ]0.0` or `Future Release`. - [ ] Celebrate shipping! From c54529de3a5da6d8f62918ee0c9090f1bc6ccf9e Mon Sep 17 00:00:00 2001 From: Joost de Valk Date: Tue, 23 Jan 2024 18:48:26 +0100 Subject: [PATCH 2/5] Update action.yml 1. Make `id` more descriptive so there's less chance of a name clash. 2. Update to version 4 of the `upload-artifact` action, as [that brings with it the rather cool option to get the artifact URL immediately](https://github.com/actions/upload-artifact/issues/50#issuecomment-1885368978). --- action.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/action.yml b/action.yml index 0402a8b..851c095 100644 --- a/action.yml +++ b/action.yml @@ -22,8 +22,8 @@ runs: shell: bash - name: Upload the archive as an artifact - id: upload - uses: actions/upload-artifact@v3 + id: upload-plugin-artifact + uses: actions/upload-artifact@v4 with: name: ${{ github.event.repository.name }} path: zipfile From 46ca41588b86eb48f9ee47b711834ad5383cf66a Mon Sep 17 00:00:00 2001 From: Jeffrey Paul Date: Tue, 19 Mar 2024 12:02:11 -0500 Subject: [PATCH 3/5] Update CHANGELOG.md --- CHANGELOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 822b7a9..9cc2c99 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,9 +4,13 @@ All notable changes to this project will be documented in this file, per [the Ke ## [Unreleased] - TBD -## [1.0.0] - 2022-12-01 +## [1.0.1] - 2024-03-20 +### Changed +- Updated to v4 of `upload-artifact`, the action now exposes the artifact URL with: `${{ steps.upload-plugin-artifact.outputs.artifact-url }}` (props [@jdevalk](https://github.com/jdevalk) via [#3](https://github.com/10up/action-wordpress-plugin-build-zip/pull/3)). +## [1.0.0] - 2022-12-01 - Initial release. [Unreleased]: https://github.com/10up/action-wordpress-plugin-build-zip/compare/stable...develop +[1.0.1]: https://github.com/10up/action-wordpress-plugin-build-zip/compare/1.0.0...1.0.1 [1.0.0]: https://github.com/10up/action-wordpress-plugin-build-zip/releases/tag/1.0.0 From f75f17289be37113ae5967efca1be927b7e67510 Mon Sep 17 00:00:00 2001 From: Jeffrey Paul Date: Tue, 19 Mar 2024 12:09:06 -0500 Subject: [PATCH 4/5] Update CREDITS.md --- CREDITS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CREDITS.md b/CREDITS.md index de1ddc8..a0f7f36 100644 --- a/CREDITS.md +++ b/CREDITS.md @@ -10,7 +10,7 @@ The following individuals are responsible for curating the list of issues, respo Thank you to all the people who have already contributed to this repository via bug reports, code, design, ideas, project management, translation, testing, etc. -[Darin Kotter (@dkotter)](https://github.com/dkotter), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul). +[Darin Kotter (@dkotter)](https://github.com/dkotter), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul), [Joost de Valk (@jdevalk)](https://github.com/jdevalk). ## Libraries From a6d6c3b28fdfcd8ebf2084cfbf1b8604a181992f Mon Sep 17 00:00:00 2001 From: Jeffrey Paul Date: Wed, 20 Mar 2024 12:28:11 -0500 Subject: [PATCH 5/5] Update and rename `no-response.yml` to `close-stale-issues.yml` --- ...no-response.yml => close-stale-issues.yml} | 30 +++++++++++-------- 1 file changed, 18 insertions(+), 12 deletions(-) rename .github/workflows/{no-response.yml => close-stale-issues.yml} (55%) diff --git a/.github/workflows/no-response.yml b/.github/workflows/close-stale-issues.yml similarity index 55% rename from .github/workflows/no-response.yml rename to .github/workflows/close-stale-issues.yml index ce0c42f..4ffcfbc 100644 --- a/.github/workflows/no-response.yml +++ b/.github/workflows/close-stale-issues.yml @@ -1,26 +1,27 @@ -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/no-response@v0.5.0 + - 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: "needs: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 @@ -28,3 +29,8 @@ jobs: 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: 'needs:feedback' + remove-stale-when-updated: true +