search

packit / packit.dev

packit.dev website content
https://packit.dev/
MIT License
9 stars 50 forks source link

Create a blog-post about pull-from-upstream workflow #496

Closed lachmanfrantisek closed 1 year ago

lachmanfrantisek commented 2 years ago

Finalise the packit/packit-service#1576 epic by creating a blog post about it. Describe how it works, how to set it up and provide some screenshots and links to the configuration.

part of packit/packit-service#1576 epic

xsuchy commented 2 years ago

I have written http://miroslav.suchy.cz/blog/archives/2022/07/14/packit_-_how_to_create_pull-request_for_fedora_from_upstream/index.html Can we use it as is? Or write it more generally?

stale[bot] commented 2 years ago

This issue has been marked as stale because it hasn't seen any activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! :unicorn: :rocket: :robot:

(Note: issues labeled with pinned or EPIC are never marked as stale.)

lachmanfrantisek commented 1 year ago

@xsuchy sorry for the late response but this is about another workflow we are currently finishing (https://github.com/packit/packit-service/issues/1576). This is to configure Packit in dist-git and "pull" the new version from upstream instead of current "push" approach of propose-downstream workflow.

(But the core functionality is shared between those two.)