Skip to content

Conversation

@mamercad
Copy link
Contributor

Might address this in #137.


# TODO: Make sure this actually constitutes "repository activity"
- name: Set this Workflow to active (prevent 60d disabling)
- name: Conditionally set this Workflow to active (attempt to prevent 60d disabling of itself)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hrm, this might only restore this workflow's state (if it's disabled) when triggered by on.workflow_dispatch...

Copy link
Member

Choose a reason for hiding this comment

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

workflow_dispatch is still a good escape hatch if all things automated fail for whatever set of reasons (like we're still figuring out what set of automation is most reliable).

@cognifloyd cognifloyd merged commit 71a08ca into StackStorm-Exchange:master Dec 21, 2022
@cognifloyd
Copy link
Member

I merged, but missed a couple issues, so I pushed a couple of follow-up commits to fix this step.

That got us to this point:
https://github.com/StackStorm-Exchange/ci/actions/runs/3746070101/jobs/6361092828#step:6:59

Cloning repos can be occassionally flaky. For the index, that's not an issue because we do it so often, that waiting a few more minutes for the next run doesn't really matter. For this workflow, I would like to avoid cloning the pack repos somehow, so that this can be more reliable.

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.

2 participants