When I started developing plugins for ClassicPress I decided that I needed to be using source control. As ClassicPress is intending to use GitHub for their plugin directory, it made sense for me to use it as well. This post is part of a series on ClassicPress Development with TortoiseGit which is a sub-series of the ClassicPress Development with GitHub series.
When you have changes committed to GitHub, you need to make a release of your plugin. Making a release has two main benefits:
- It labels the files in the repository with a tag making it easy to download a particular version of the plugin.
- You can upload a zip file containing the plugin folder giving a zip file which users can download and upload to their ClassicPress site.
To create a release, open the GitHub repository page and click the releases link at the top (ringed in red):
As there are no releases, click the Create a new release option button the middle of the screen (once there is at least one release the create new release button is in the top right):
Enter the Tag Version (for developing with ClassicPress, you should use Semantic Versioning), Release title and description of the release (you can use markdown).
Drag your zip file into the Attach binaries by dropping them here or selecting them box and click the Publish release button:
Your release will now be live and available for people to see and download the file.
As time goes by you will create additional releases, all of which will be listed on the releases page:
ClassicPress Development with GitHub
| ClassicPress Development with TortoiseGit |
|---|
| What is TortoiseGit? |
| Install Git for Windows |
| Install TortoiseGit for Windows |
| First run |
| Update |
| Clone Repository |
| Commit |
| Revert Last Commit |
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.