This is an automated email from the ASF dual-hosted git repository. wave pushed a change to branch fix-metadata in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
discard 977878c djlint comments discard b56b1e7 Clean up for djlint discard 4415019 Fix titles and descriptions discard b96aea4 Merge branch 'main' of https://github.com/apache/tooling-trusted-releases discard c420a23 Update the Playwright test imports to match conventions discard ae65d6e Add a couple of simple public route tests add 28a28a9 Ensure that paths are tracked correctly when creating an SBOM file add 5d85a8b Add pip-audit to the standard lints add 2a3873a Add a couple of simple public route tests add 35d194c Fix titles and descriptions add ff489b3 Clean up for djlint add 2dccf91 djlint comments This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (977878c) \ N -- N -- N refs/heads/fix-metadata (2dccf91) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .pre-commit-config.yaml | 4 ++++ atr/post/draft.py | 5 +++++ 2 files changed, 9 insertions(+) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
