Repository navigation
Replies: 5 comments 1 reply
|
This would be a great feature. Until it's fully supported by Forge, you could collect the needed info (issue number is on current line or in frame title, depending on view, etc.) and call the |
|
I hesitate to add this feature because it is only the first step toward full support for projects and I don't have the bandwidth to implement that any time soon. I believe to remember that there already is a package that adds support for projects, though I might be imagining things. |
|
I too could use something like this! I see |
|
Is this feature still way down in your backlog? This is the only feature that is making me still having to open up github.com. At my org we use projects to organize us |
|
I plan to move away from forges such as Github. I was planning to move to Codeberg, but am not sure anymore, that is enough. Developments over the last few and especially the last year, forced me to invest in defense, and I am increasingly worried that having a world-writable public todo list puts maintainers under constant stress. I'll keep maintaining Forge; after all most (i.e., currently all) of my packages are still hosted on Github and I also want to keep using it for repositories on Github, which are owned by other people. But new features are becoming increasingly unlikely. I am least motivated to add features like this, which increase lockin. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I plan to use kanban in my current collaborative project so i miss an opportunity to assign issue to the board (they call boards "Projects" on github...). Please consider including this little feature.
All reactions