Skip to content

Conversation

@jessfraz
Copy link
Contributor

In the future we will likely only want to do this on tag push, but for
now while changes are being made frequently for dev purposes, let's do
it on every push to main, and of course if someone makes a PR to the
workflow so we can test.

Closes #597

Do not merge til after #751

I'm open to changing the name of the action, I didn't spend much time thinking about it.

In the future we will likely only want to do this on tag push, but for
now while changes are being made frequently for dev purposes, let's do
it on every push to main, and of course if someone makes a PR to the
workflow so we can test.

Closes #597

Signed-off-by: Jess Frazelle <github@jessfraz.com>
Copy link
Contributor

@zephraph zephraph left a comment

Choose a reason for hiding this comment

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

I, for one, welcome our robot overlords.

Looks good. The concurrency key is a nice touch, I need to keep that one in mind.

Co-authored-by: Justin Bennett <oss@just-be.dev>
@zephraph zephraph merged commit 0344a70 into main Mar 14, 2022
@zephraph zephraph deleted the update-spec branch March 14, 2022 15:32
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.

automatically open a PR to update the spec in the docs repo when it changes in this repo

3 participants