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

action for verifying author of vendor.schema.json #516

Merged
merged 7 commits into from
Oct 8, 2024

Conversation

chirag-jn
Copy link
Collaborator

@chirag-jn chirag-jn commented Oct 7, 2024

Fixes #297

I have added a workflow to verify author of vendor.schema.json.
Steps followed:

  1. Discover if changes have been made in vendor.schema.json
  2. Fetch the commit author
  3. Fetch authors in @superlinked/vdb-table-maintainers team
  4. Verify if the commit author is a part of the team
  5. If the author is not part of the team, then send a message in the PR to request the author to start a new issue for the change.

@chirag-jn chirag-jn requested a review from AruneshSingh October 7, 2024 21:54
Copy link

github-actions bot commented Oct 7, 2024

This PR contains schema changes. Please note that schema changes affect all vendors simultaneously.
@ Could you create a separate issue to discuss the necessity for this schema change with @vdb-table-maintainers? This will help ensure proper review and coordination.

Copy link

github-actions bot commented Oct 7, 2024

This PR contains schema changes. Please note that schema changes affect all vendors simultaneously.
@chirag-jn Could you create a separate issue to discuss the necessity for this schema change with @vdb-table-maintainers? This will help ensure proper review and coordination.

@AruneshSingh AruneshSingh merged commit 8d78473 into main Oct 8, 2024
1 check passed
@AruneshSingh AruneshSingh deleted the schema-authorize branch October 8, 2024 07:48
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.

Add GH action to protect from schema changes
2 participants