-
Notifications
You must be signed in to change notification settings - Fork 11
Creating a Release
corsacca edited this page Sep 16, 2021
·
7 revisions
- Update the Version number in disciple-tools-plugin-starter-template.php
- Commit your code
This option has github actions automatically create a release based on the configuration options in .github/workflows/release.yml.
The action waits for a tag to be pushed to the repository and creates a release when one is.
- Check the
.github/workflows/release.ymlfile is updated
- that
disciple-tools-plugin-starter-templateis replaced with your plugin-name - that line 26
cp -r ...includes all the files you want in your release and remove any folder that were deleted
- When you want to create a release, create a tag with the current version and push the tag:
git tag -a 0.2 -m "0.2"
git push --tags origin master
- github will automatically create a release based on the tag and zip and attach the plugin with only the file you with to include
- Update version number in
[*plugin-name*].phpand commit changes to Github.- In the comment at the top
- Download master [.zip] from the plugin Github repo, rename .zip to
disciple-tools-[*plugin-name*].zip - Unzip the .zip file
- Rename
[*plugin-name*]-masterto[*plugin-name*]removing-master - Re-zip the file
- Create a new release in GitHub with the new version number (eg: 1.3.1) and release description.
- Attach the plugin .zip file to the new version release.
- Update your published release description with what changed
- update the
version-control.json
-
versionline -
last_updatedline - make sure the other lines are correct and point to your repository