Skip to content

Add workflow to prevent changes to Extensions list#1976

Draft
heitortsergent wants to merge 6 commits intomainfrom
hts/add-extensions-workflow
Draft

Add workflow to prevent changes to Extensions list#1976
heitortsergent wants to merge 6 commits intomainfrom
hts/add-extensions-workflow

Conversation

@heitortsergent
Copy link
Collaborator

What?

Add a workflow to prevent users from changing the explore.md file. The file should only be updated by maintainers, or the Extension Registry workflow in this repo.

Checklist

  • I have used a meaningful title for the PR.
  • I have described the changes I've made in the "What?" section above.
  • I have performed a self-review of my changes.
  • I have run the npm start command locally and verified that the changes look good.
  • I have made my changes in the docs/sources/k6/next folder of the documentation.
  • I have reflected my changes in the docs/sources/k6/v{most_recent_release} folder of the documentation.
  • I have reflected my changes in the relevant folders of the two previous k6 versions of the documentation (if still applicable to previous versions).
  • I have made my changes in the docs/sources/k6/next folder of the documentation.

Related PR(s)/Issue(s)

#1961

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@heitortsergent
Copy link
Collaborator Author

@codebien would you be able to help me with this? 🙏

I'm wondering if this looks right / if the workflow should be running on this PR already. 🤔

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