Per project configuration
See original GitHub issueThe config file currently lives in ~/.backport, which is fine, but it would be awesome if we could check-in the config for a project (like the repo location, branches, etc)
Issue Analytics
- State:
 - Created 6 years ago
 - Comments:14 (12 by maintainers)
 
Top Results From Across the Web
Per project configuration · oracle/opengrok Wiki - GitHub
Property Type Meaning
annotationCacheEnabled boolean enable annotation cache, generated during reindex
handleRenamedFiles boolean disables or enables handling of renamed files
historyEnabled boolean enables or disables history...
Read more >Per-project configuration, Storybook support for Angular 12 ...
Per-project Configuration. Traditionally, in Nx workspaces, configuration for all projects is all contained in workspace.json and nx.json files.
Read more >Project Configuration File Format - Gerrit Code Review
The project.config file contains the link between groups and their permitted actions on reference patterns in this project and any projects that inherit...
Read more >git: how to have per project configuration? - Stack Overflow
Just use the git config command without the --global parameter. Instead of git config --global user.name "lang2". Type git config user.name ...
Read more >Configuration file per project - Studio - UiPath Community Forum
Configuration: Scope to a specific project or release. Like the Config.xlsx, having the same role as Config.xlsx from Reframework. The ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Btw. I’m thinking about renaming “versions” to “branches”, since that’s really what they are. Any objections?
@spalger @epixa I ended up with a compromise, so the project config (
.backportrc.json) behaves as described in https://github.com/sqren/backport/issues/27#issuecomment-348350190, but can be overridden by the global config (.backport/config.json). By default the global config only contains the required fields (accessTokenandusername), so most users will never override the project specific settings likelabels- I see it as a hidden feature for power users.There is an open PR https://github.com/sqren/backport/pull/29 and I’ve published a beta version that you can install if you want to try it out:
npm install backport@2.1.1-betaWith the beta you can add the following
.backportrc.jsonto the kibana repo:and simplify your global config
~/.backport/config.json: