Block a user
Update license tag to Zlib AND (Unlicense OR MIT-0) AND MIT
v2:
- Use
Unlicensein place ofPublic-Domainwhich is what is specified indr_mp3.hanyway.
Update license tag to Zlib AND (Public-Domain OR MIT-0) AND MIT
obs-staging-bot: allow build-disabling repositories in the QA projects
obs-staging-bot: allow forking projects and build-disabling their repositories
v3:
- Addressed review comments, including moving the ForkOrganization inside the per-product QA definitions
- Added documentation
I've split the BuildDisableRepos (which is the most useful…
obs-staging-bot: allow build-disabling repositories in the QA projects
obs-staging-bot: allow forking projects and build-disabling their repositories
yes, it totally does, thanks
epaolantonio
created branch epaolantonio/builddisable in epaolantonio/autogits
2026-01-21 19:11:13 +01:00
epaolantonio
pushed to epaolantonio/builddisable at epaolantonio/autogits
2026-01-21 19:11:13 +01:00
obs-staging-bot: allow forking projects and build-disabling their repositories
It is not a big deal to handle the "fork" (which is just a branch push) elsewhere, the main user of this is the pkglistgen bot that should have anyway enough permissions to write to the "staging"…
obs-staging-bot: allow forking projects and build-disabling their repositories
Ah, I see what you mean. The config file taken is the one from the source PR rather than the target branch, so that is indeed an issue. Let me think about it.
obs-staging-bot: allow forking projects and build-disabling their repositories
Thanks for the review! Sorry, I totally missed the README.md.
So maybe this forking behaviour needs to be done differently... this is the only major issue I have adding this functionality…
obs-staging-bot: allow forking projects and build-disabling their repositories
v2:
- Restored
common.LogDebug("Setup QA sub projects")which was dropped by mistake - Fixed minor typo in the
ForkOrganizationexplanation
obs-staging-bot: allow forking projects and build-disabling their repositories