affinitybridge / git-bpf Goto Github PK

Sorry if I'm missing it, but I've tried:

git recreate-branch rc -x 'USXXXX-Bad_Feature_1', 'USXXXX-Bad_Feature_2'
git recreate-branch rc -x USXXXX-Bad_Feature_1, USXXXX-Bad_Feature_2
git recreate-branch rc -x USXXXX-Bad_Feature_1 USXXXX-Bad_Feature_2
git recreate-branch rc -x 'USXXXX-Bad_Feature_1, USXXXX-Bad_Feature_2'
git recreate-branch rc -x ['USXXXX-Bad_Feature_1', 'USXXXX-Bad_Feature_2']

What should the syntax be?

The article at https://www.acquia.com/blog/pragmatic-guide-branch-feature-git-branching-strategy indicates that your scripts used to take a file which contained the list of branches to exclude, but that doesn't appear to be the case with the new Gem. Is that right? 'Cause....that'd be nice.

Thanks,

Brandon

The init operation allows you to pass in -r or --remote-name

http://rubydoc.info/gems/git_bpf/1.0.1/Init

however the main docs page says that the remote must be named origin.

I'm getting the next error when i run "git-bpf-init" in windows 10:

fatal: No such section!
C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/git-helpers.rb:16:in ``': No such file or directory - /usr/bin/tput cols (Errno::ENOENT)
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/git-helpers.rb:16:inwidth' from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/git-helpers.rb:36:in ohai'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/commands/init.rb:94:in`execute'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/gitflow.rb:197:in `block in run'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/gitflow.rb:183:in`catch'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/lib/git_bpf/lib/gitflow.rb:183:in `run'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/git_bpf-1.0.1/bin/git-bpf-init:6:in`block in <top (required)>'

can anybody help me ?

Im getting the following error in Windows 7 when I run the init command.

NotImplementedError: symlink() function is unimplemented on this machine
symlink at org/jruby/RubyFile.java:1677
execute at C:/jruby-1.6.7/lib/ruby/gems/1.8/gems/git_bpf-1.0.1/lib/git_bpf/com
mands/init.rb:99
run at C:/jruby-1.6.7/lib/ruby/gems/1.8/gems/git_bpf-1.0.1/lib/git_bpf/lib
/gitflow.rb:197
catch at org/jruby/RubyKernel.java:1197
run at C:/jruby-1.6.7/lib/ruby/gems/1.8/gems/git_bpf-1.0.1/lib/git_bpf/lib
/gitflow.rb:183
(root) at C:/jruby-1.6.7/lib/ruby/gems/1.8/gems/git_bpf-1.0.1/bin/git-bpf-ini
t:6

I have problems when git_bpf is installed in the same gemset as bundler, I get the error

/Users/Infoactive/.rvm/gems/ruby-2.0.0-p353@global/gems/rubygems-bundler-1.4.2/lib/rubygems-bundler/noexec.rb:75:in setup': undefined methodname' for #Array:0x1091f0810 (NoMethodError)
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `map'

I had both git_bpf and bundler installed in my global gemset, if I remove bundler, then git_bpf works.

Any idea on how to make the two coexist?

pollinator:features davetarc$ git recreate-branch QA -x f-585_orphaned_reference_fields --list
==> 1. Processing branch 'QA' for merge-commits...
Branches to be merged:

• f-585_orphaned_reference_fields
• f-747_action_email_scheduler
• f-749_consultation_due_date_shuffle
• f-794_fix_async_layer_spinner
• f-657_minor_deceased_facet
• f-780_species_type_unset_on_interview_import
• f-790_security_updates
• f-646_communications
• hotfix-792_intersection_block_labels
• f-748_new_access_field
• f-744_open_actions_block
• f-644_due_date_color
• f-418_species_confidential_field
• f-784_location_photo_var
• f-522_phpexcel_version
• f-685_respondent_avatar_missing
• f-793_tu_value_csv_updates
• f-676_consult_review_action
  pollinator:features davetarc$ git recreate-branch QA -x f-585_orphaned_reference_fields
  ==> 1. Processing branch 'QA' for merge-commits...
  Warning: The following branches will be merged when the new QA branch is created:
• f-747_action_email_scheduler
• f-749_consultation_due_date_shuffle
• f-794_fix_async_layer_spinner
• f-657_minor_deceased_facet
• f-780_species_type_unset_on_interview_import
• f-790_security_updates
• f-646_communications
• hotfix-792_intersection_block_labels
• f-748_new_access_field
• f-744_open_actions_block
• f-644_due_date_color
• f-418_species_confidential_field
• f-784_location_photo_var
• f-522_phpexcel_version
• f-685_respondent_avatar_missing
• f-793_tu_value_csv_updates
• f-676_consult_review_action

If you see something unexpected check:
a) that your 'QA' branch is up to date
b) if 'master' is a branch, make sure it is also up to date.
Warning: If there are any non-merge commits in 'QA', they will not be included in 'QA'. You have been warned.

Proceed with QA branch recreation? [y/N]
y
==> 2. Creating backup of 'QA', 'BRANCH-PER-FEATURE-PREFIX-QA'...
==> 3. Creating new 'QA' branch based on 'master'...
==> 4. Merging in feature branches...

• 'f-747_action_email_scheduler'
• 'f-749_consultation_due_date_shuffle'
• 'f-794_fix_async_layer_spinner'
• 'f-657_minor_deceased_facet'
• 'f-780_species_type_unset_on_interview_import'
• 'f-790_security_updates'
• 'f-646_communications'
• 'hotfix-792_intersection_block_labels'
• 'f-748_new_access_field'
• 'f-744_open_actions_block'
• 'f-644_due_date_color'
  Staged 'modules/features/consultation/includes/consultation.api.inc' using previous resolution.
  Staged 'themes/custom/ieg_cis/styles/less/children/nodes.less' using previous resolution.
• 'f-418_species_confidential_field'
• 'f-784_location_photo_var'
• 'f-522_phpexcel_version'
• 'f-685_respondent_avatar_missing'
• 'f-793_tu_value_csv_updates'
• 'f-676_consult_review_action'
  Staged 'modules/features/consultation/consultation.ds.inc' using previous resolution.
  ==> 5. Cleaning up temporary branches ('BRANCH-PER-FEATURE-PREFIX-QA').