[meta] Proposal to support custom vendor headers #2122
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
Directory custom should contain vendor specific custom headers that are considered vendor internal and should not be available to public, but they still can have metadata generated for them for vendor internal use.
|
@JaiOCP please check this out, cherry pick on your side, and refactor your custom headers for specified format, to check if this solution works for you |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
For testing purpose
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@JaiOCP please give me feedback if this is what you have been looking for. I would like to merge this change |
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.
Directory custom should contain vendor specific custom headers that are considered vendor internal and should not be available to public, but they still can have metadata generated for them for vendor internal use.
Check doc/custom-headers/ for more info