Add blog post about release synchronization under the hood#1149
Conversation
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 10s |
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 05s |
majamassarini
left a comment
There was a problem hiding this comment.
Nice! Thank you!
I was wondering if we should create a diagram from this document and link it at the bottom. I think it could be useful, to have something more visual.
| a [release-monitoring.org](https://release-monitoring.org) event, configured in dist-git | ||
| - action - list of commands that can replace the default Packit implementation of a certain step | ||
| of the process | ||
| - hook - action that does nothing by default |
There was a problem hiding this comment.
| - hook - action that does nothing by default | |
| - hook - action that does nothing by default and is meant to be customized by the users |
There was a problem hiding this comment.
not a big deal, from my point of view, for a new user, it is not so explicit.
| <!--truncate--> | ||
|
|
||
| `propose_downstream` and `pull_from_upstream` share most of the implementation. One notable | ||
| difference is that `pull_from_upstream` always uses the downstream spec file as a base for |
There was a problem hiding this comment.
Should we add that it takes the specfile in the rawhide branch? Or is it too much detail?
There was a problem hiding this comment.
Did you mean config file?
There was a problem hiding this comment.
I could mention it, on the other hand, it feels a bit out of scope, this isn't an onboarding document.
Let me try to add something. |
Signed-off-by: Nikola Forró <nforro@redhat.com> Assisted-by: Claude Opus 4.6 via Claude Code
It is not actually called and it only confuses users. Signed-off-by: Nikola Forró <nforro@redhat.com> Assisted-by: Claude Opus 4.6 via Claude Code
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 08s |
I've added a mermaid diagram at the end, not sure if that's what you meant, but I think it brings some value. |
No description provided.