-
Notifications
You must be signed in to change notification settings - Fork 59.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign all tags by default #35186
base: main
Are you sure you want to change the base?
Sign all tags by default #35186
Conversation
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
@sih4sing5hong5 Thanks so much for opening a PR! I'll get this triaged for review ✨ Additionally, viewing deployment seems to be working now! Can you check once more? 💛 |
|
Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀 |
Refer: https://stackoverflow.com/a/56979390
Why:
Closes: #35185 35185
What's being changed (if available, include any code snippets, screenshots, or gifs):
Add the command for set the configure about signing tags. Like #21497 .
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.