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

add a publish script; prep to publish #267

Merged
merged 2 commits into from
Jan 26, 2023

Conversation

devoncarew
Copy link
Member

@devoncarew devoncarew commented Jan 25, 2023

  • add a publish script
  • prep to publish 1.17.1

@devoncarew devoncarew changed the title blast_repo fixes add a publish script; prep to publish Jan 26, 2023
@github-actions
Copy link

publish action:

  • package:collection: 1.17.1 is ready to publish; after merging, tag with v1.17.1 to trigger publishing


on:
pull_request:
branches: [ master ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does publish run on a PR?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It validates the info - so you know that it's something you could publish - and it writes a comment to the PR telling you the git tag to use if everything looks good for publishing.

So, validation on PRs, and, publishing on well-formed commits.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clever clever...

@devoncarew devoncarew merged commit a566328 into master Jan 26, 2023
@devoncarew devoncarew deleted the blast_repo-2023_01_25T23_52_30 branch January 26, 2023 18:04
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.

None yet

2 participants