-
-
Notifications
You must be signed in to change notification settings - Fork 926
Ignore issues in archived repositories #1272
Comments
@mmoayyed link to repo? This is probably only possible with GraphQl and we will wait another few months before attempting to switch again |
Here is the issue in an archived repo by me: Thanks for the feedback. |
Could you elaborate on how could you archive an issue? I'm not aware of something called archive in GitHub and never heard of. |
Archiving a repository is not presently open to public, and is something made available to participants of Github's "early access program", which is somewhat private. If you get in touch with github and request access, they will more than likely get you into the program (I am not sure about the selection process). Then you'd see this: |
Im in early program but never got an email about it lol. Well, if you still can see it on your profile then you should see it in here as well, I'm not sure if there is a filter for it provided by the api, I'll check later if there is one I'll add it. |
@k0shk0sh it was added to graphql timeline |
@k0shk0sh This still applies to PRs, the ones in archived repos are still shown in the app's main panel. One's PRs page uses the |
FastHub Version: 4.5.6
Android Version: 8.0.0 (SDK: 26)
Device Information:
If I look at issues I have created over time, I see a number of them that now belong to archived repositories. I can no longer close or update issues because the repository is read only now. I suggest such issues be filtered and skipped in the issues screen.
The text was updated successfully, but these errors were encountered: