![]() Placing a config directly in a project is nice because it allows customizing the ticket prefix on a per-project basis. If configs are found both within the project and in your home directory, then both will be used, with precedence given to the project config. You can place your config file directly in your project so that your whole team can take advantage of it, or in your home directory for your personal use. This means you can configure pushup via any standard configuration method. ![]() Pushup uses cosmiconfig for configuration file support. □ The pushup init command will create a configuration file for you via interactive prompts Config file location ➜ pushup 123 # Where 123 is your ticket numberīranch 'myBranch ' set up to track remote branch 'zp-NVM-123-myBranch ' from 'origin '. Install pushup globally with either npm or yarn: Pushup-cli solves that problem by allowing you to create a short local branch name, and automatically publishing a remote branch name that meets your teams standards. Even terminal auto-complete can't help very much because the repetitive part of the branch name tends to be at the beginning, and for auto-complete to work you at least have to type it out until you get to a unique portion of the branch name.Your branch names become long and a pain to type.For some reason it's always harder than it should be to remember the damn format you're supposed to use.But as you've probably found (if you've made your way here), that method has some drawbacks: ![]() To follow this standard, devs will often create a local branch in that format and then just push it up like normal. MLD-419-add-graphql-support # Where MLD-419 is a ticket number Zp/my-branch # Where zp are someone's initials ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |