-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
Allow to add a new component to a published repo #1341
Allow to add a new component to a published repo #1341
Conversation
c6c6c0d
to
603ad6d
Compare
what a great feature to have :-) thanks a lot ! the feature/debian branch is moving to go 1.22, so I would merge this one afterwards... |
603ad6d
to
609af87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks !
please rebase ! then we can merge... |
This commit modifies the behavior of the publish switch method in the way, that also new components can be added to an already published repository. It is no longer necessary to drop and recreate the whole publish. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
7cf7d11
to
d1168d6
Compare
I rebased and force pushed to your branch (since it allowed me to do that :-) ... |
@neolynx |
See #1345 for the new APT repos containing a CI build with this change! |
That are really great news 😃. Thank you very much for all your efforts spent so far for improving, fixing, enhancing and getting Aptly back to life. |
Fixes #832, #1242
Description of the Change
This commit modifies the behavior of the publish switch method in the way, that also new components can be added to an already published repository. It is no longer necessary to drop and recreate the whole publish.
Checklist
AUTHORS