Extend the current content for Octo to include step by step details for
- creating an issue
- commenting on an issue
- updating an issue
C-r to refresh an issue, e.g. when updated outside of Neovim or if editing issue in Neovim and the red change line is not updating
:w command seems to sync reliably but not so much SPC w. More testing is required.
Issues
Create an issue for the current Git project.
Select an issue template if that repository provides them.
Enter the title of the issue
NOTE: consider using conventional commits for structure of the commit message
Edit the issue as with any other file in Neovim.
Ensure the changes are within the change marker in the margin.

GitHub command line
Include gh commands that are not yet implemented in Octo
Edit issue number 80 and add yourself @me to the Assignees meta data:
gh issue edit 80 --add-assignee "@me"
Set the default repository to use for issues (if there are more than one and origin isnt used). A popup appears with a list of remotes to choose from.
Add a label
Add a type
e.g. set Type to doc
Add to Project
Extend the current content for Octo to include step by step details for
C-rto refresh an issue, e.g. when updated outside of Neovim or if editing issue in Neovim and the red change line is not updating:wcommand seems to sync reliably but not so muchSPC w. More testing is required.Issues
Create an issue for the current Git project.
Select an issue template if that repository provides them.
Enter the title of the issue
Edit the issue as with any other file in Neovim.
Ensure the changes are within the change marker in the margin.
GitHub command line
Include
ghcommands that are not yet implemented in OctoEdit issue number 80 and add yourself
@meto the Assignees meta data:gh issue edit 80 --add-assignee "@me"Set the default repository to use for issues (if there are more than one and origin isnt used). A popup appears with a list of remotes to choose from.
Add a label
Add a type
e.g. set Type to
docAdd to Project