Upload metadata function for track2 #17082
Conversation
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
| # Check whether MANIFEST.in includes _meta.json | ||
| require_meta = "include _meta.json\n" | ||
| manifest_file = os.path.join(package_folder, "MANIFEST.in") | ||
| if not os.path.exists(manifest_file): |
There was a problem hiding this comment.
If MANIFEST.in doesn't exit, do we nee create one?
There was a problem hiding this comment.
I think we don't need to do it at this script. This file should be created from template. If not, it maybe something wrong when creating this package at first time.
|
/check-enforcer evaluate |
No description provided.