Module: Subversion::SvnCommand::Commit

Defined in:

lib/svn-command/svn_command.rb

Overview

---

Instance Method Summary

• #__broken ⇒ Object (also: #__expect_to_break_tests, #__knowingly_committing_broken_code)

  Use this flag if you are about to commit some code for which you know the tests aren’t or (probaby won’t) pass.

• #__skip_notification ⇒ Object (also: #__covert)

  Use this flag if you don’t want a commit notification to be sent out.

Instance Method Details

#__broken ⇒ Object Also known as: __expect_to_break_tests, __knowingly_committing_broken_code

Use this flag if you are about to commit some code for which you know the tests aren’t or (probaby won’t) pass. This may cause your continuous integration system to either skip tests for this revision or at least be a little more leniant towards you (a slap on the wrist instead of a public flogging, perhaps) when it runs the tests and finds that they are failing. You should probably only do this if you are planning on making multiple commits in rapid succession (sometimes Subversion forces you to do an intermediate commit in order to move something that’s already been scheduled for a move or somethhing, for example). If things will be broken for a while, consider starting a branch for your changes and merging the branch back into trunk only when you’ve gotten the code stable/working again. (See svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html)

# File 'lib/svn-command/svn_command.rb', line 230

def __broken
  @broken = true
end

#__skip_notification ⇒ Object Also known as: __covert

Use this flag if you don’t want a commit notification to be sent out.

# File 'lib/svn-command/svn_command.rb', line 216

def __skip_notification
  @skip_notification = true
end