Add Lineage configuration. #22
Merged
Conversation
This file contains 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
felddy
requested review from
dav3r,
hillaryj,
jsf9k,
mcdonnnj and
a team
as code owners
jsf9k
approved these changes
May 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🗣 Description
Add a Lineage configuration file. This allows the Lineage GitHub Action to identify the relationships between repositories and propagate changes via pull requests.
💭 Motivation and Context
This reduce the amount of time we spend creating PRs, and allow changes to propagate downstream in a timely manner.
🧪 Testing
Tested on multiple repositories.
📷 Screenshots (if appropriate)
🚥 Types of Changes
✅ Checklist