GJS issueshttps://source.small-tech.org/gnome/gnomit/gjs/-/issues2018-08-21T17:29:25Zhttps://source.small-tech.org/gnome/gnomit/gjs/-/issues/3Enhancement: Ability to commit and push (if remote is set)2018-08-21T17:29:25ZAral BalkanEnhancement: Ability to commit and push (if remote is set)https://source.small-tech.org/gnome/gnomit/gjs/-/issues/14Get git-related data from git itself instead of parsing the auto-generated co...2018-10-21T19:49:04ZAral BalkanGet git-related data from git itself instead of parsing the auto-generated commit messageRe features like getting the current branch name, etc.,Re features like getting the current branch name, etc.,https://source.small-tech.org/gnome/gnomit/gjs/-/issues/15Add option to automatically add sign-off statement to commit messages2018-08-21T17:20:39ZAral BalkanAdd option to automatically add sign-off statement to commit messagesAs suggested via Mastodon: “Would be nice if it would come with a config option to automatically add a sign-off statement at the end so that I will never forget '-s' in the future.”
https://mastodon.social/@bjoern/100556447266760002As suggested via Mastodon: “Would be nice if it would come with a config option to automatically add a sign-off statement at the end so that I will never forget '-s' in the future.”
https://mastodon.social/@bjoern/100556447266760002https://source.small-tech.org/gnome/gnomit/gjs/-/issues/22Set Gnomit as the default Git editor as part of the Flatpak installation process2018-08-21T17:20:16ZAral BalkanSet Gnomit as the default Git editor as part of the Flatpak installation processAral BalkanAral Balkanhttps://source.small-tech.org/gnome/gnomit/gjs/-/issues/23Benchmark startup time2018-08-21T17:20:35ZAral BalkanBenchmark startup timeThe startup time of the Flatpak version is considerably (and visibly) slower than running the GJS script directly. This has a marked negative impact on the experience.
Benchmark the startup to see if it is entirely Flatpak overhead (whi...The startup time of the Flatpak version is considerably (and visibly) slower than running the GJS script directly. This has a marked negative impact on the experience.
Benchmark the startup to see if it is entirely Flatpak overhead (which might be solved by https://blogs.gnome.org/alexl/2018/01/16/fixing-flatpak-startup-times/) or whether the script itself also executes slower when running under Flatpak.Aral BalkanAral Balkanhttps://source.small-tech.org/gnome/gnomit/gjs/-/issues/33Add support for global settings editing2019-02-02T23:21:42ZAral BalkanAdd support for global settings editingCurrently breaks when you:
`git config --global -e`
![Screenshot_from_2019-02-02_23-19-46](/uploads/afccd7fb44deb982be796d638308f59c/Screenshot_from_2019-02-02_23-19-46.png)Currently breaks when you:
`git config --global -e`
![Screenshot_from_2019-02-02_23-19-46](/uploads/afccd7fb44deb982be796d638308f59c/Screenshot_from_2019-02-02_23-19-46.png)Aral BalkanAral Balkanhttps://source.small-tech.org/gnome/gnomit/gjs/-/issues/34Warning on merge message2019-05-12T16:37:12ZAral BalkanWarning on merge messageMerge messages are handled properly but there is a warning thrown. Add explicit support.
`Warning: unknown Git commit type encountered in: /home/aral/ind.ie/hypha/web-server/.git/MERGE_MSG`Merge messages are handled properly but there is a warning thrown. Add explicit support.
`Warning: unknown Git commit type encountered in: /home/aral/ind.ie/hypha/web-server/.git/MERGE_MSG`Aral BalkanAral Balkanhttps://source.small-tech.org/gnome/gnomit/gjs/-/issues/35If previous message included an octothorpe (hash), it gets treated as a comment2020-03-11T15:10:56ZAral BalkanIf previous message included an octothorpe (hash), it gets treated as a commentOnly hashes at the start of lines should be interpreted as comments.
## To reproduce
1. Commit using message: 'Closes #1: something'
2. `git commit --amend`
## What should happen
The message should read “Closes #1: something” and be ...Only hashes at the start of lines should be interpreted as comments.
## To reproduce
1. Commit using message: 'Closes #1: something'
2. `git commit --amend`
## What should happen
The message should read “Closes #1: something” and be editable.
## What actually happens
The message reads “Closes ” and the hash onwards is shown on the next line as a comment and is not editable.Aral BalkanAral Balkan