You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before using the packit_config_checker script again I suggest to:
The script is now looking for the last year active projects so I ended up with some old configs not updated by the script, one project turned out to be still actively maintained (the configs were already downloaded some time ago). We should probably warn the user to download the configs in a clean directory and probably it is safer to get the configs for all the projects (not just those active the latest year).
We should update the already created packit forks for github and gitlab (pagure should be already implemented).
Probably could be useful to be able to force-push an already create PR with some changes if we realize there is a mistake for one or more projects.
the script always propose PR in upstream, when it exists, but projects can have the sync_from_downstream job enabled! So there is a chance that it will be later overwritten...
even though the upstream project has merged the Packit proposed upstream PR, until propose-downstream is run and the packit created PRs are merged, the downstream config may remain broken and out of sync.
The text was updated successfully, but these errors were encountered:
Before using the
packit_config_checker
script again I suggest to:sync_from_downstream
job enabled! So there is a chance that it will be later overwritten...propose-downstream
is run and the packit created PRs are merged, the downstream config may remain broken and out of sync.The text was updated successfully, but these errors were encountered: