Week 41 (October 7th – October 13th)
- Pull requests created by Packit in Fedora dist-git now contain information in their descriptions that Packit force-pushes to its own PR branches when a new upstream PR lands. (packit#2780)
pyforgejo import that was introduced with a new upstream release. (packit/ogr#949)PACKIT_COPR_BUILD_ID in the Testing Farm tests. (packit/packit-service#2857)fast_forward_merge_into syntax via --dist-git-branches-mapping in dist-git init. (packit#2456)We have added support for retriggering jobs that are configured for commit and release trigger. Retriggering can be done via commit comments on the relevant commit, using the usual comments, such as /packit build or /packit test, but the branch or tag need to be specified like this (without the arguments, we will default to commit trigger for the default branch of the repository):
/packit build --commit <branch-name>
or
/packit build --release <tag-name>
There is a new method for getting a single commit comment, supporting also retrieval and adding reactions in GitHub. (ogr#865)
We have improved the feedback for the Open Scan Hub job. You can now see if the scan is in a pending, running, canceled, failed, or successful state.
A failed or canceled scan is shown as neutral and does not cause your pull request validation to fail. (packit-service#2543)
/packit test) now accepts --env option(s)
to override environment variables passed to Testing Farm.
(packit-service#2583)sync-release or bodhi_update jobs. (packit#2442)packit validate-config now checks for the existence of the downstream package. (packit#2436)--resolve-bug switch (comments accept comma-separated list of bugs, CLI accepts the switch multiple times (also -b)).
(packit#2428 and packit-service#2560)packit init now adds working directories that are used in packit prepare-sources into the .gitignore file in the same directory where Packit config resides. (packit#2431)