Skip to content

DOCS-323 Deprecate FEAT tag and friends.#398

Merged
LegacyKing merged 2 commits intoPCGen:masterfrom
LiaungYip:DOCS-323
Jul 26, 2015
Merged

DOCS-323 Deprecate FEAT tag and friends.#398
LegacyKing merged 2 commits intoPCGen:masterfrom
LiaungYip:DOCS-323

Conversation

@LiaungYip
Copy link
Copy Markdown
Contributor

No description provided.

LegacyKing added a commit that referenced this pull request Jul 26, 2015
DOCS-323 Deprecate FEAT tag and friends.
@LegacyKing LegacyKing merged commit 75134b1 into PCGen:master Jul 26, 2015
@LegacyKing
Copy link
Copy Markdown
Member

Just one thing to be mindful of - notice the branch wasn't made from the "master" but brought forward the other commit changes. Not an issue in this case, but just something to be aware of. Cheers,

@LiaungYip
Copy link
Copy Markdown
Contributor Author

I did it intentionally - the commits both touched the same files, and didn't want to create a manual merge situation again. What's the etiquette for separate commits touching the same file?

@LegacyKing
Copy link
Copy Markdown
Member

That's a bit tricky. Ideally, each issue in a PR should be separated by the changes. I'm guilty of cross-polluting my commits in some cases, so not unheard of. However, each branch PR should focus on the specific issue being addressed. The first commit was all about the UDAM change (also, something to note, is you want to reference the issue in the title, like you've done, so the JIRA catches the change. Which is the main reason to keep issues separated. Keeps from JIRA capturing the wrong commits. If the cross pollution is unavoidable. Separate them out by different commits as best you can, and then do the PR for them all. At least with separate commits, it is easier to cherry pick the changes if an issue arises. Cheers,

@LiaungYip LiaungYip deleted the DOCS-323 branch August 16, 2015 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants