Arlo for WordPress Plugin
This repository contains the source code for the Arlo for WordPress plugin. The plugin is maintained on GitHub and deployed to the WordPress plugin repository using GitHub Actions. This README serves as a guide for contributors to make changes and deploy the plugin.
Table of Contents
Prerequisites
- Git installed on your local machine
- A GitHub account
- Basic understanding of the OneFlow branching strategy
Getting Started
- Fork the repository into your GitHub account.
- Clone your forked repository onto your local machine using
git clone <repository_url>
.
- Set up a new remote named
upstream
to track the original repository: git remote add upstream git@github.com:ArloSoftware/arlowp-plugin.git
.
- Ensure your fork is up-to-date with the original repository by executing
git pull upstream master
before making any changes.
Making Changes
- Create a new feature branch based on the current
master
branch. Name your branch according to the task you're working on, e.g., git checkout -b feature/shortcode-extension master
.
- Make your changes in the newly created branch.
- Commit your changes using descriptive commit messages.
- Push your branch to your forked repository:
git push origin <branch_name>
.
- Open a pull request on the original repository to merge your changes into the
master
branch. Make sure to provide a detailed description of your changes.
Deploying the Plugin
To deploy a new release of the plugin, follow these steps:
- Create a release branch from the current
master
branch, e.g., git checkout -b release/4.1.6 master
.
- Update the version number in the
readme.txt
file and include the changes made in the release.
- Update the
CHANGELOG.txt
file to include the changes made in the new release.
- Update the version number in
arlo-for-wordpress.php
.
- Update the
arlo-for-wordpress-settings.php
file to include the changes made in the new release.
- Update the version number in the
includes/arlo-version-handler.php
file.
- Commit your changes with a descriptive commit message.
- Push the release branch to your forked repository:
git push origin <branch_name>
.
- Open a pull request on the original repository to merge the release branch into the
master
branch. Provide a detailed description of the release.
- Once the pull request is approved and merged, create a new release on GitHub by following these steps:
- Go to the repository's "Releases" tab.
- Click on "Draft a new release" or "Create a new release."
- Enter the new version number as the tag, e.g.,
v4.1.6
.
- Select the appropriate target branch, usually
master
.
- Write a title and release notes, including the changes made in the new release.
- Click "Publish release."
- The GitHub Action will automatically deploy the plugin to the WordPress plugin repository upon creating the new release.
- To double check that the deployment has succeeded go to Arlo for WordPress Plugin Page and check the Version is updated, you may have to wait a few minutes and then do a hard refresh.
Resources