minor: Version 1.2.1

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git 2.6+ -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely
• Do not run remote instances of VS Code while the script is running! If it is running, the next fetch will sweep up the changes.

How to Use

More information on how to use the script is available on the Wiki page -- How To Use

Updates

This release fixes a major bug in v1.2.0. See change log below for more details:

• 🐛 git cmd to support older versions of git
• ☑️ check dev branch gets pushed before deleting

major: Version 1.2.0

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git capability -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely
• Do not run remote instances of VS Code while the script is running! If it is running, the next fetch will sweep up the changes.

How to Use

More information on how to use the script is available on the Wiki page -- How To Use

Updates

This release fixes a major bug in v1.1.0. See change log below for more details:

• 🐛 Issues with committing and pushing changes back to the remote repository has been addressed
• 🔦 You can now just fetch changes from the web server by committing them to the dev branch and pushing back to the remote repository
• 🥅 You can now soft stop the script if changes are found
• ✏️ Some launch arguments have changed!
• 🎨 General bug fixes and tidying up of the script

major: Version 1.1.0

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git capability -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely

How to Use

More information on how to use the script is available on the Wiki page -- How To Use

Updates

This release fixes a major bug in v1.0.1, improves efficiencies in the script, and decreases the number of errors tossed from unnecessary actions.

• 🍻 PR #29 removing wildcard handler, still having issues
  • 🔥 #18 improvement: option to delete remote Live branch if no merge
  • 🧠 #15 improvement: break up methods and optargs to support actual choices
  • ✅ #28 enhancement: Add more validation for option arguments
    note: there are are no plans now to delete any branches remotely
  • 📝 #16 improvement: add ability to set commit message using optarg
  • 🏅 #14 improvement: add more checks for required arguments to launch

minor: Version 1.0.2

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git capability -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely

Updates

This release fixes a major bug in v1.0.1, improves efficiencies in the script, and decreases the number of errors tossed from unnecessary actions.

• ♻️💡 imp order of methods and properties and more line comments (#17)
• 🐛 Remote boolean was being set in reverse! (#20)

minor: Version 1.0.1

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git capability -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely

Updates

• PR #7 ✨ added better logic checks for reducing command errors for remotes

major: Version 1.0.0

✨ Automate your WordPress and git repository release pipeline
If there's SSH & Git, you can sync WordPress and Azure DevOps using git.

Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.

Requirements:

• Web server have git capability -- think this is the most important one
• A method to store your secrete variables such as
  • username
  • password/token
• SSH access to execute scripts on WordPress server
  • note: cron can serve as a slower alternative to SSH
• Some kind of CI pipeline or cron job to hook into after a branch update event triggers an agent to run the script remotely