Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename branch in push-asset-readme-update.yml #79

Merged
merged 1 commit into from
Feb 8, 2021

Conversation

jeffpaul
Copy link
Member

@jeffpaul jeffpaul commented Feb 8, 2021

Description of the Change

Direct change to trunk to ensure the push-asset-readme-update.yml action will trigger when I make a follow up PR to trunk to adjust the tested-up-to version.

Alternate Designs

Wait until a formal release to have all of develop merge into trunk and apply this update as well as the subsequent one to bump the tested-up-to version.

Benefits

Ensures we can push asset/readme changes in the interim and before our next plugin release.

Possible Drawbacks

none identified

Verification Process

Manually reviewed via the GitHub web UI.

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests passed.

Applicable Issues

n/a

Changelog Entry

n/a

@jeffpaul jeffpaul added this to the 1.1.0 milestone Feb 8, 2021
@jeffpaul jeffpaul self-assigned this Feb 8, 2021
@jeffpaul jeffpaul merged commit 8f6b9e4 into trunk Feb 8, 2021
@jeffpaul jeffpaul deleted the chore/rename-branch-trunk branch February 8, 2021 23:00
@jeffpaul jeffpaul modified the milestones: 1.1.0, 1.0.3 Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant