When updating local config file, some config gets lost #43

tagoro9 · 2017-05-16T04:21:54Z

It happens with a local config file and a failed jira login with the global user / password. If there is a local config file with other config (i.e. github) it will get lost.

* If the config file had info in a different path than the data being updated if was removed. Fixes #43.

* fix(config): do not use empty object when updating local config file * Now the issue types are fetched from Jira and stored in the config file with a short name. There are some defaults to match the existing behavior (feature and story => f, task => c). In any other cases, the first letter of the type is used for the short name. * Users can define the templates in the config file under jira => templates => branch. For now this is the data passed to those templates: issue.shortName, issue.key and issue.sanitizedSummary. In order to access them from the template, { and } must be used to interpolate. Fixes #43, #38.

tagoro9 added the Type: Bug label May 16, 2017

tagoro9 added a commit that referenced this issue Jun 15, 2017

fix(config): do not use empty object when updating local config file

eaad6ef

* If the config file had info in a different path than the data being updated if was removed. Fixes #43.

tagoro9 mentioned this issue Jun 15, 2017

feat(start): allow user to define branch name templates #47

Merged

tagoro9 closed this as completed in #47 Jun 15, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

When updating local config file, some config gets lost #43

When updating local config file, some config gets lost #43

tagoro9 commented May 16, 2017

When updating local config file, some config gets lost #43

When updating local config file, some config gets lost #43

Comments

tagoro9 commented May 16, 2017