Format JSON in container-registry-delete.md #25
Conversation
|
Learn Build status updates of commit 414d3cc: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@microsoft-github-policy-service agree |
|
@rammba : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
@tejaswikolli-web Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Learn Build status updates of commit feae498: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @tejaswikolli-web |
github-actions
bot
removed
the
inactive
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
rammba
force-pushed
the
features/container-registry-delete
branch
from
feae498 to
d268fe6
Compare
|
Learn Build status updates of commit d268fe6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Hello @tejaswikolli-web, sorry for pinging but I don't know how to remove inactive tag. This is ready for review. |
github-actions
bot
removed
the
inactive
|
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
No description provided.