Module: Subversion::SvnCommand::Commit
- Defined in:
- lib/subwrap/svn_command.rb
Overview
Instance Method Summary collapse
-
#__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.
-
#__doesnt_need_review ⇒ Object
Skips e-mail and marks reviewed=true Similar to the ‘reviewed’ command, which just marks reviewed=true.
-
#__include_externals ⇒ Object
:todo: svn doesn’t allow you to commit changes to externals in the same transaction as your “main working copy”, but we can provide the illusion that this is possible, by doing multiple commits, one for each working copy/external.
-
#__shirk_blame ⇒ Object
Causes blame/author for this commit/file to stay the same as previous revision of the file Useful to workaround bug where fixing indent and other inconsequential changes causes you to be displayed as the author if you do a blame, [hiding] the real author.
-
#__skip_notification ⇒ Object
(also: #__covert, #__minor_edit, #__minor)
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)
342 343 344 |
# File 'lib/subwrap/svn_command.rb', line 342 def __broken @broken = true end |
#__doesnt_need_review ⇒ Object
Skips e-mail and marks reviewed=true Similar to the ‘reviewed’ command, which just marks reviewed=true
350 351 352 |
# File 'lib/subwrap/svn_command.rb', line 350 def __doesnt_need_review @__doesnt_need_review = true end |
#__include_externals ⇒ Object
:todo: svn doesn’t allow you to commit changes to externals in the same transaction as your “main working copy”, but we can provide the illusion that this is possible, by doing multiple commits, one for each working copy/external.
When this option is used, the same commit message is used for all commits.
Of course, this may not be what the user wants; the user may wish to specify a different commit message for the externals than for the “main working copy”, in which case the user should not be using this option!
361 362 363 |
# File 'lib/subwrap/svn_command.rb', line 361 def __include_externals @include_externals = true end |
#__shirk_blame ⇒ Object
Causes blame/author for this commit/file to stay the same as previous revision of the file Useful to workaround bug where fixing indent and other inconsequential changes causes you to be displayed as the author if you do a blame, [hiding] the real author
367 368 369 |
# File 'lib/subwrap/svn_command.rb', line 367 def __shirk_blame @shirk_blame = true end |
#__skip_notification ⇒ Object Also known as: __covert, __minor_edit, __minor
Use this flag if you don’t want a commit notification to be sent out.
326 327 328 |
# File 'lib/subwrap/svn_command.rb', line 326 def __skip_notification @skip_notification = true end |