Nikola Forró

I don't think there is anything else in changelog entries that would prevent parsing a spec file than unescaped macros, so a simple substitution from `%` to `%%` should work....

I think the documentation is clear, however, commit message titles can contain troublesome characters as well, and so can the output of the `changelog-entry` action. We could improve the documentation,...

I think this is semi-related to the work I've been doing in https://github.com/packit/specfile/pull/101. But I'd have to make it more general so it can work also with `%setup` arguments.

I believe the second pull-from-upstream run is supposed to be: ``` 4. packit -d --config ~/packit_ds_nmstate.yml pull-from-upstream --resolve-bug RHEL-19409 ``` And the bug ID has to be different than the...

I can reproduce it on Fedora with CLI as well, however when commenting `/packit pull-from-upstream --resolved-bugs rhbz#NNNNNN` on a PR, Packit service amends the existing commit and force pushes to...

I think this would be a big quality of life improvement. Here is a snippet from an [existing](https://src.fedoraproject.org/rpms/micropipenv/blob/2961e90f2f860338508ce83d841ab724c4649c6d/f/.packit.yaml) Packit config: ```yaml actions: changelog-entry: - bash -c '[ -n "$PACKIT_RESOLVED_BUGS" ]...

We decided to add a new option, e.g. `--preserve-[spec-]source`.

Just a note - that condition seems a bit off. First, there is no `%changelog` in the first branch of the condition block, so if it evaluates to true, there...

The problem happens when the upstream spec is copied, excluding changelog. In this case, only the last 3 lines of the file are excluded (starting with `%changelog`), so the condition...

On the other hand, if it looked like this: ```spec %if 0%{?centos}