Re: Strange behavior of GitHub

Frank, That’s correct. You must *never* push directly to the mirror repositories on Github, nor may you use any of the Github merge or edit tools. Push only to code and it will automatically update Github. I think we can set up the GnuCash Github repositories so that only the special user

Re: Strange behavior of GitHub

A quick look at https://lists.gnucash.org/pipermail/gnucash-patches/2017-July/date.html#start shows only gnucash-docs master: Multiple changes pushed Frank H.Ellenberger There seems to be no hook, which pulls changes on github to code. Together with my git remote configuration: origin

Re: Branch of gnucash-docs on code.gnucash.org

Um, we DO build the maint branch of gnucash-docs. -derek "Frank H. Ellenberger" writes: > Hi Derek, > > I am wondering if building the master branch of gnucash-docs is such a > good solution. > > we have one or two documented features of the 2.8 serie in master

Strange behavior of GitHub

Hi all, Dmitry watched, that his PRs disappeared from Maint after I merged them in Master. So, what happened? He sent PR 100-104 to github I pulled them via https://github.com/Gnucash/gnucash-docs/pull/... sequently into maint, after each calling locally: (with git checkout maint) git pull

Re: Intended behavior of automatic decimal point (bug 120940)

Sumit,  As I understand it, the example you gave  (560 becomes 5.60) is intended behavior. And, as far as I am concerned, the explanation in the help is sufficient, if not inspiring.  It seems to me the problem in the underlying bug is that the decimal algorithm needs to be applied after any

Intended behavior of automatic decimal point (bug 120940)

​Hi, In an attempt to fix a long-standing bug ( https://bugzilla.gnome.org/show_bug.cgi?id=120940), I looked at the code and have a question on intended behavior of automatic decimal point. From the doc (http://gnucash.org/viewdoc.phtml?doc=help), I see this description for automatic decimal