Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customization #37

Open
ymoisan opened this issue Feb 22, 2016 · 1 comment
Open

Customization #37

ymoisan opened this issue Feb 22, 2016 · 1 comment
Assignees
Milestone

Comments

@ymoisan
Copy link

ymoisan commented Feb 22, 2016

Duplicate of Oslandia#43

@ymoisan ymoisan modified the milestones: 0.7, 0.6 Feb 22, 2016
@gignacnic
Copy link

This is just to document if we do want instead of using registration key, use a JSON parameter stored in Database to disable branch mode.
Once we created the historisation, we push a JSON value (branch: false) to the revisions table, after when a user tried to create a branch from the trunk_head, it shows a message to user that the DB has disable branch mode.
In summary, to disable the branch mode in the plugin, it is done during historisation, we add a JSON parameters in the initial commit in the DB trunk_head (table revisions, revision=1, field commit_msg, value = {"commit_msg":"initial commit", "branch":"false"}). In the add_branch function in versioning_base.py it validates the JSON parameters as in revision=1, if it is there and value:false a message shows up saying : "Branch cannot be created, this feature has been disable in the head revision table on initial commit").
If we do want to reactivate the branch mode in the DB, we take off this JSON parameters in the table revision and it goes back to the default process (branch can be created).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants