Require owner review and clarify MIT licensing - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assign all files, including ownership and workflow configuration, to @jesseoue for review. Preserve the existing MIT license and copyright notices, explain third-party licensing obligations, and separate permission to reuse a copy from permission to change the canonical repository. The organization-profile repository gains the missing standard MIT license.
Where applicable, pin workflow actions, remove unnecessary bot write access, and require the maintainer-controlled release environment before publication. Release references must belong to reviewed main history. Validation workflows run for every PR so required checks cannot be omitted by path filters.
Validation: ownership/license/public-file checks, n8n package contents, and generated GTM artifacts checked locally. No releases or paid API calls. GitHub protection settings are applied separately after these policy files are merged.