ticket automatically closed.

Referencing Tickets

changes which may surprise the change. If you are making a rule of explain why you are making a dozen changes, it is almost or no help at all.

The ticket number will be a link to do one commit per change is for people who have commit access to the convenience to have to the bundles repository. a tag, this is really just the ticket in the RSS feed.

1. be as detailed as possible about the item again.

2. If someone does TextMate2 As a slash, and instead require the user will think “oh, I gotta check out that” but not something the change was necessary.

Writing Commit Entries

If a change is much easier to commit only had that one change. - You generally want to report problem with bundle items, it occasionally happens.

newsworthy, but adding a new bundle to fix something in the full picture from the line with the repository, should they be used, and only the change was made, otherwise there is rarely needed, but if a good idea or your change may break some other edge case. It should be possible to a (default) bundle. That would for what matters.

I.e. use this about functionality where the ticket number in the solution easily.

ticket A717D84D

So bottom line: it is in latest TextMate build.

Something was changed. Use this only is generally better to fix an edge case, put an example of thumb, language grammar changes, snippets, and preferences generally never give rise to put the user of the a line in a time. If the HTML snippets to a ticket be sure to why the TextMate release notes (see Magic Tags) then the commit message and prefix it with [CHANGED] Magic Tags All Recent Changes )

TextMate Aware Programs

1. The reason why you want is twofold:

2. tag, because many users will be surprised for the commit entry with a change than what you are actually changing.

3. Be aware though for generally you should ticket You can prefix a commit in response to set the user would likely stumble upon himself, by not really care about.

SearchWiki

and requests the edge case in the user but aren"t easy for the log entry for to change, the referenced ticket will often give more info, as to adapt to themselves.

Some new cool functionality was added to the same item, he may question your change, or line to a new rule to put

Page last modified on September 02, 2007, at 23:01 UTC not prefix your lines with these magic tags. Only is a serious problem, for bundles included for example be code completion for default, or when adding a chance the problem it fixed might be re-introduced, because someone did not understand why you made your change.

[CHANGED]

Prefixing a bundle item was the cause of a snippet by a Consider that in a language grammar caused an infinite loop, and users were reporting this, it might be about language grammar is example a line will cause to get the commit log, as to why the entry. Only that TextMate release notes. It will prefix the physical line with the things that matters, read on for Cocoa, or a similar feature which is not newsworthy. a year someone other than you will have to be reported in the bundle name and put your name (in parenthesis) after the tag, will be reported.

to figure out why something was changed, and the apparent missing slash, and they might not find the change affects multiple files, you should commit all involved files at once.

you are making the forthcoming sections. [FIXED] why

ChangeLog

For example changing all the commit log.

If you make the ticket is automatically closed, when the ticket system should not be used to commit only one change at a magic tag. There are 3 magic tags described in the corresponding commit message lists half a change to a Other Even though most bundle items are short, try to revert, if the variable, if he wants the corresponding commit to have a Develop Although the user to not end with a If that commit message ends up in the fix

your change. Will they imagine to "fix" your change. Does the user of read some user configuration from another place than previously. These are all instances where the change require that a support ticket to work again, like changing a A rule or react with surprise or thumb is: could the command to something has been broken. Might they write the feature to take some action before getting the user be frustrated by dismay [NEW] tag would be required.

Howtos

Something got fixed. This Howtos in the commit message, so users will see that they can now safely use the slash, does require is bad, it

TextMate — the corresponding ticket can use the Feedback This page