Replies: 4 comments 4 replies
-
Above I mentioned |
Beta Was this translation helpful? Give feedback.
-
I don't remember "Org support" to be an often requested feature. While I understand the appeal of "Org support", I don't plan to implement anything in that direction any time soon, I just have the bandwidth for that and fear that some minor steps in that direction wouldn't be all that useful in isolation. There is already a package that provides Github-Org integration but I don't remember its name and it has been abandoned years ago. Still, you might want to locate and investigate that package and maybe adapt it to use forge as an intermediate layer. |
Beta Was this translation helpful? Give feedback.
-
This is the other one I know of:
https://github.com/dakra/org-github/blob/master/org-github.el
|
Beta Was this translation helpful? Give feedback.
-
Oh this one, there a new repository for it:
https://github.com/arbox/org-sync
|
Beta Was this translation helpful? Give feedback.
-
It would be nice to use the power of Org for working with Magit Forge.
I don't see mention of Org in Discussions, but note that many Issues mention Org, but I think this is only because it's listed in the debug strings pasted by users. This suggests many Magit and Forge users are also Org users.
One feature could be bulk viewing and editing of Issues (tags, times, sizes, assignees, etc.) via Org column view.
Another feature could be viewing Issues (single or groups) as a standard Org file, using tags and properties, allowing edits that can be pushed back to the Forge. This is similar to how https://github.com/nyyManni/ejira presents Jira issues
It is already possible to edit issues in Org mode and have them converted to Markdown automagically.
Forge allows private notes (and other metadata for a topic?). It would be nice to support SCHEDULE and DEADLINE data privately, so that topics can appear in an Org Agenda view.
Beta Was this translation helpful? Give feedback.
All reactions