You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allowing for the / prefix to be parsed as namespace?
This would allow for managing modules across multiple namespaces. Otherwise I'm not sure if it's possible to do and creating a modulesync_confg for each namespace seems like a poor way to manage something like this.
Any other suggestions welcome.
The text was updated successfully, but these errors were encountered:
Also in order to keep remote modulesync branches up to date with master or dev branches before pushing these changes wouldn't the remote branch need to be a parameter in order to rebase against?
So something like:
if ! upstream_branch
default_upstream_branch = 'master'
else
default_upstream_branch = upstream_branch
end
repo.checkout(branch)
repo.pull('origin', default_upstream_branch)
repo.push('origin', branch)
Because currently I believe branch is set to options[:branch] which if it's modulesync then it will pull changes for modulesync and then push back to modulesync but doesn't resync against master or in some cases based on development workflow dev branch
cdenneen
changed the title
namespaced managed_modules
rebase from defined branch - managed_modules
Jul 11, 2017
instead of providing
namespace
inmodulesync.yml
couldmanaged_modules.yml
allow for the following syntax:Allowing for the
/
prefix to be parsed as namespace?This would allow for managing modules across multiple namespaces. Otherwise I'm not sure if it's possible to do and creating a modulesync_confg for each namespace seems like a poor way to manage something like this.
Any other suggestions welcome.
The text was updated successfully, but these errors were encountered: