p-s to react to new commits in a d-g branch and be able to do builds

[TomasTomecek]

TODO

• react to push events on dist-git
• be able to submit koji builds if a new push comes
• also implement service's side of https://github.com/packit/packit/issues/264

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.
We are doing this to be sure that the issue is still relevant. Anyone can comment to remove the stale state. (The issues marked with pinned, security, bug or EPIC label
are not considered stale.)

[TomasTomecek]

I recall we got a request for this in jira, so let's keep this open.

[TomasTomecek]

hello @lachmanfrantisek :)

[lachmanfrantisek]

Still relevant. Will be possible after we finish the koji jobs from upstream.

[stale]

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! 🦄 🚀 🤖

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

[lachmanfrantisek]

I would really like to see this.

[stale]

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! 🦄 🚀 🤖

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

[TomasTomecek]

I wish we could make this into next GSoC

[stale]

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! 🦄 🚀 🤖

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

[lachmanfrantisek]

This will be a really nice feature to have but we have a lot of work with higher priority to do -- dashboard, quicker responses, bugs, UX...

New features like this are sadly on the bottom of our backlog. But as I wrote above, I would still like to see this implemented.

[stale]

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! 🦄 🚀 🤖

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

[lachmanfrantisek]

Closing in favour of #55