-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #73 from Automattic/update/plugin-plumbing-only
Plumbing updates
- Loading branch information
Showing
23 changed files
with
510 additions
and
187 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 |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# See https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners | ||
* @Automattic/vip-bistro |
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 |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: bug | ||
assignees: ingeniumed, smithjw1, alecgeatches, chriszarate | ||
|
||
--- | ||
|
||
**Describe the bug** | ||
A clear and concise description of what the bug is. | ||
|
||
**To Reproduce** | ||
- Include what kind of a post has caused this problem | ||
|
||
**Expected behavior** | ||
A clear and concise description of what you expected to happen. | ||
|
||
**Actual behavior** | ||
A clear and concise description of what actually happened. | ||
|
||
**Version of the plugin** | ||
Version of the plugin | ||
|
||
**Additional context** | ||
Add any other context about the problem here. Please be careful to not share any confidential information here. |
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 |
---|---|---|
@@ -0,0 +1,17 @@ | ||
## Description | ||
|
||
A few sentences describing the overall goals of the Pull Request. | ||
|
||
Should include any special considerations, decisions, and links to relevant GitHub issues. | ||
|
||
## Steps to Test | ||
|
||
Outline the steps to test and verify the PR here. | ||
|
||
Example: | ||
|
||
1. Check out PR. | ||
1. Run `npm run build`. | ||
1. Test the thing.` | ||
1. Verify cookies are delicious. | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Release steps | ||
|
||
## 1. Create a release branch | ||
|
||
1. Before merging a feature, create a release branch for the next target version, e.g. | ||
|
||
```bash | ||
git checkout trunk | ||
git checkout -b planned-release/0.2.1 | ||
``` | ||
|
||
2. In GitHub, select the base branch as the `planned-release/...` branch. | ||
3. Merge feature branches into the `planned-release/...` branch. | ||
|
||
## 2. Update build files | ||
|
||
```bash | ||
composer install --no-dev | ||
``` | ||
|
||
Note: If new production dependencies have been added, modify the root `.gitignore` file to include new `vendor/` subfolders. | ||
|
||
Now commit these build changes in. | ||
|
||
## 3. Bump plugin version | ||
|
||
1. When the version is ready for release, inside the `planned-release/...` branch, bump the version number in `vip-decoupled.php`. | ||
2. Create a PR for the planned release branch (e.g. "Planned release 0.2.1") and merge to `trunk`. | ||
|
||
## 4. Tag branch for release | ||
|
||
1. In `trunk`, add a tag for the release: | ||
|
||
```bash | ||
git checkout trunk | ||
git pull | ||
git tag -a <version> -m "Release <version>" | ||
|
||
# e.g. git tag -a 1.0.2 -m "Release 1.0.2" | ||
``` | ||
|
||
2. Run `git push --tags`. | ||
|
||
## 5. Create a release | ||
|
||
1. In the `vip-decoupled-bundle` folder, run this command to create a plugin ZIP: | ||
|
||
```bash | ||
git archive --prefix "vip-decoupled-bundle/" <version> -o vip-decoupled-bundle-<version>.zip | ||
|
||
# e.g. git archive --prefix "vip-decoupled-bundle/" 1.0.2 -o vip-decoupled-bundle-1.0.2.zip | ||
# | ||
# Creates a ZIP archive with the prefix folder "vip-decoupled-bundle/" containing files from tag 1.0.2 | ||
``` | ||
|
||
2. Visit the [vip-decoupled-bundle create release page](/~https://github.com/automattic/vip-decoupled-bundle/releases/new). | ||
3. Select the newly created version tag in the dropdown. | ||
4. For the title, enter the release version name (e.g. `1.0.2`) | ||
5. Add a description of release changes. | ||
6. Attach the plugin ZIP. | ||
7. Click "Publish release." |
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.