Skip to content

Config with default template 2.6.1.dev0#428

Merged
gforcada merged 3 commits intomasterfrom
config-with-default-template-2.6.1.dev0
Apr 10, 2026
Merged

Config with default template 2.6.1.dev0#428
gforcada merged 3 commits intomasterfrom
config-with-default-template-2.6.1.dev0

Conversation

@mauritsvanrees
Copy link
Copy Markdown
Member

Made with latest plone.meta 2.x plus tox-uv from plone/meta#247

@mister-roboto
Copy link
Copy Markdown

@mauritsvanrees thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@mauritsvanrees mauritsvanrees force-pushed the config-with-default-template-2.6.1.dev0 branch from 52f5cff to c0acced Compare April 10, 2026 08:16
@mauritsvanrees
Copy link
Copy Markdown
Member Author

I also ran bumpversion --final. I have rebased to do this as the first commit, as it adds [ci skip] to its commit message. At least that is how I have configured zest.releaser in my ~/.pypirc.

@gforcada gforcada merged commit b199a96 into master Apr 10, 2026
10 of 12 checks passed
@gforcada gforcada deleted the config-with-default-template-2.6.1.dev0 branch April 10, 2026 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants