Default repository in GitHub Project? #60258
Replies: 17 comments 7 replies
-
|
Currently, GitHub Projects does not have a default repository setting for creating issues. You need to select the repository each time when adding an item to a project board. However, you can consider submitting a feature request to GitHub Support or the GitHub Community forums to suggest adding this feature. It can enhance the user experience for managing work in a single repository. |
Beta Was this translation helpful? Give feedback.
-
|
Having a default Repository setting would be super nice for smaller, simpler teams. When a default repository is set, I would love to see quick links to different pages in the repository like Pull Requests, Code, Actions, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Weirdly enough it seems to currently use the earliest repository (creation date) as default. So, the current state is not only inconvenient, but also buggy. |
Beta Was this translation helpful? Give feedback.
-
|
@Th3S4mur41 is correct, the problem is not only lack of ability to set default repo for a project, it do have a default repo selected whenever creating an issue, even the repo was already archived. It means, everytime I create an issue, have to popup the repo dropdown list and then select the only one which is not archieved. In my case, I have three projects in my organization and only one is active, but it just default to the one which shouldn't be there. |
Beta Was this translation helpful? Give feedback.
-
|
This is super annoying! Also adding that if you archive the "earliest" repo, create issue dialog still wants to create issues on that repo. Deleting the "earliest" repo is the current, well..., workaround. |
Beta Was this translation helpful? Give feedback.
-
|
@queenofcorgis any updates? This issue is super annoying |
Beta Was this translation helpful? Give feedback.
-
|
can we get this in please |
Beta Was this translation helpful? Give feedback.
-
|
The current way to enter issues just has too much friction, too many clicks. I don't need to select a repo and template every time. |
Beta Was this translation helpful? Give feedback.
-
|
In itself a reason to not use GitHub Projects |
Beta Was this translation helpful? Give feedback.
-
|
Please add this feature, it would make our lives much easier |
Beta Was this translation helpful? Give feedback.
-
|
We’ve also been troubled by this issue for a long time, but recently we finally found a simple workaround: Rename your default repo (for example, from A to B), then create a new repo called A. After that, in your local code repository (which was originally pointing to A), run: Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Currently , GitHub Projects (beta or classic ) don't support setting a "default repository " directly . Projects can include issues or PRs from multiple repositories which makes flexible across orgs or teams if your projects mostly tracks issues from a single repository , use filters like ; Features Request Idea : It would be really helpful if GitHub allowed setting a "default repo" for a project so new issues could automatically link to it , especially for mono-repo teams Unitil then , saved filters and views can help simulate this behavior |
Beta Was this translation helpful? Give feedback.
-
|
+1! this is much needed. Is making my life miserable in an early stage company with projects across different repos |
Beta Was this translation helpful? Give feedback.
-
|
GitHub recently rolled out changes to bypass the repo selection screen entirely. While this addresses the complaints of people who wanted to minimize clicks, it has created a new pain point - namely, that the GitHub-selected unchangeable default repo is often not the right one. This is particularly painful when the default repo is public, but there are private repos in the project. In the short time since this change, I have seen this lead to numerous instances where public issues have been created with sensitive content. GitHub project management honestly continues to disappoint. It's buggy, slow, and randomly missing important functionality. |
Beta Was this translation helpful? Give feedback.
-
|
Also, if no default repo is configured for the project, it would be handy if the repo dropdown at least remembered your most recent selection(s), so when frequently creating multiple tickets, each contributor could at least benefit from some personal UX caching. There's already user specific tracking of recently viewed projects, so adding tracking for recently selected repos mapped for each project doesn't seem much of a stretch from a UX pattern. I'd just like the actively selected repo from the initial state of the dropdown during ticket creation to be the most recently selected option - per user, or overridden to be the default repo via project's setting. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone knows when was this added? This perfectly solves my problems! |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Feature Area
Projects
Body
👋 Hello,
I'd like to be able to create Issues in a default repo when I'm using GitHub Projects, I'm not sure if it is possible. Is it?
Specifically if I click
+ Add ItemI always have to select my repository but with a default option I wouldn't need to do this.Ideally, I think it would be good to be able to set a default repository for a project in the Settings page for a Project.
https://github.com/users/<username>/projects/<project_number>/settingsIf not is this something that can be done now, could it be considered as a feature request? It's a very minor thing but I think it would improve the user experience for people who are using a GitHub Project to manage work in one repository.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions