Some projects do not have issues enabled

[lachmanfrantisek]

• We traceback when we want to create an issue on repository that has no issue tracker (e.g. https://github.com/dhodovsk/packit)
• we need to add this functionality to the ogr:
  Requires: Add property and raise specific exception when issues are disabled ogr#664

[sentry-io]

Sentry issue: RED-HAT-0P-2AK

[TomasTomecek]

what's the expected workflow here? how do we let the user know that something's wrong?

[lachmanfrantisek]

what's the expected workflow here? how do we let the user know that something's wrong?

• We probably cannot do anything. We can set the status for commits but that's all we can do. (At least for PRs, we can add a comment.)
• Do we have some real example? (That one was only a fork created by Dominika.)
• It looks like the solution for us is to not fail in this case.

[TomasTomecek]

+1 let's just fix the traceback

[sentry-io]

Sentry issue: RED-HAT-0P-2MQ

[sentry-io]

Sentry issue: PACKIT-SERVICE-3VK

e.g. https://github.com/rhinstaller/anaconda

[lachmanfrantisek]

After some time we do have some real examples, e.g. all distgit repositories (e.g. https://src.fedoraproject.org/rpms/packit/) that use Bugzilla instead of the Pagure issues.

[sentry-io]

Sentry issue: PACKIT-SERVICE-3W9

[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.)