Skip to content

Revert accidental doc removal #2304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 6, 2017
Merged

Revert accidental doc removal #2304

merged 1 commit into from
Jul 6, 2017

Conversation

ChrisMaddock
Copy link
Member

Another @oznetmaster special -acdc547#diff-773ff02e2f8e671f005e32bcf2e9d03eL44

#2296 seems to have caught something it couldn't.

ChrisMaddock referenced this pull request Jul 6, 2017
Copy link
Member

@mikkelbu mikkelbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikkelbu mikkelbu merged commit b763bc2 into master Jul 6, 2017
@mikkelbu mikkelbu deleted the ChrisMaddock-patch-1 branch July 6, 2017 13:24
@ChrisMaddock
Copy link
Member Author

Thanks @mikkelbu 🙂

@ChrisMaddock ChrisMaddock added this to the 3.8 milestone Jul 6, 2017
@ChrisMaddock ChrisMaddock self-assigned this Jul 6, 2017
@mikkelbu
Copy link
Member

mikkelbu commented Jul 6, 2017

@ChrisMaddock Should it not be an issue that is assigned to a milestone? (this is the only PR with a milestone AFAICT)

@ChrisMaddock
Copy link
Member Author

If there's both Issue and PR, assign just the issue. If there's only a PR, assigning the PR is fine.

The tool that generates the release notes doesn't mind which one is there, but of course we don't want any duplicates. 🙂

@mikkelbu
Copy link
Member

mikkelbu commented Jul 6, 2017

Understood 👍

@CharliePoole
Copy link
Member

Having an issue is only important for the humans, especially if there is a need to decide what to do. Also OOF you see a bug and don't plan to fix it in the next few minutes.

@jnm2
Copy link
Contributor

jnm2 commented Jul 8, 2017

Heh, it wasn't accidental. But 👍

@ChrisMaddock
Copy link
Member Author

ChrisMaddock commented Jul 9, 2017

Ah, ok! I thought it was an odd regex malfunction. ;-) Either way - it's documented now!

@jnm2
Copy link
Contributor

jnm2 commented Jul 9, 2017

I thought it was an odd regex malfunction.

People say that about me a lot. 😁 ;-)

OmicronPersei added a commit to OmicronPersei/nunit that referenced this pull request Jul 27, 2017
Revert accidental doc removal

nunit@acdc547#diff-773ff02e2f8e671f005e32bcf2e9d03eL44
Merge pull request nunit#2304 from nunit/ChrisMaddock-patch-1

Revert accidental doc removal
Tests now work, namespace issue was preventing building.


Merge remote-tracking branch 'nunit-upstream/master' into issue-1151


Extended CollectionTally to keep track of both extra and missing items.


Basic collection differences now displayed.


Some test refactoring.


Hopefully caught them all this time.


Added test to ensure CollectionEquivalentConstraint returns a CollectionEquivalentConstraintResult.


Fixed some broken tests.


Add test to ensure that CollectionEquivalentConstraint makes use of new feature by default.


Added test files to all test projects.


Removed unnecessary include in csproj and removed unnecessary using statements in CollectionEquivalentConstraintResultTests.


Cleaned up some of the tests, added one more.


Added warning disable for linux builds.
OmicronPersei added a commit to OmicronPersei/nunit that referenced this pull request Jul 27, 2017
Revert accidental doc removal

nunit@acdc547#diff-773ff02e2f8e671f005e32bcf2e9d03eL44
Merge pull request nunit#2304 from nunit/ChrisMaddock-patch-1

Revert accidental doc removal
Tests now work, namespace issue was preventing building.


Merge remote-tracking branch 'nunit-upstream/master' into issue-1151


Extended CollectionTally to keep track of both extra and missing items.


Basic collection differences now displayed.


Some test refactoring.


Hopefully caught them all this time.


Added test to ensure CollectionEquivalentConstraint returns a CollectionEquivalentConstraintResult.


Fixed some broken tests.


Add test to ensure that CollectionEquivalentConstraint makes use of new feature by default.


Added test files to all test projects.


Removed unnecessary include in csproj and removed unnecessary using statements in CollectionEquivalentConstraintResultTests.


Cleaned up some of the tests, added one more.


Added warning disable for linux builds.
OmicronPersei added a commit to OmicronPersei/nunit that referenced this pull request Jul 27, 2017
Revert accidental doc removal

nunit@acdc547#diff-773ff02e2f8e671f005e32bcf2e9d03eL44
Merge pull request nunit#2304 from nunit/ChrisMaddock-patch-1

Revert accidental doc removal
Tests now work, namespace issue was preventing building.


Merge remote-tracking branch 'nunit-upstream/master' into issue-1151


Extended CollectionTally to keep track of both extra and missing items.


Basic collection differences now displayed.


Some test refactoring.


Hopefully caught them all this time.


Added test to ensure CollectionEquivalentConstraint returns a CollectionEquivalentConstraintResult.


Fixed some broken tests.


Add test to ensure that CollectionEquivalentConstraint makes use of new feature by default.


Added test files to all test projects.


Removed unnecessary include in csproj and removed unnecessary using statements in CollectionEquivalentConstraintResultTests.


Cleaned up some of the tests, added one more.


Added warning disable for linux builds.
OmicronPersei added a commit to OmicronPersei/nunit that referenced this pull request Jul 28, 2017
Revert accidental doc removal

nunit@acdc547#diff-773ff02e2f8e671f005e32bcf2e9d03eL44
Merge pull request nunit#2304 from nunit/ChrisMaddock-patch-1

Revert accidental doc removal
Tests now work, namespace issue was preventing building.


Merge remote-tracking branch 'nunit-upstream/master' into issue-1151


Extended CollectionTally to keep track of both extra and missing items.


Basic collection differences now displayed.


Some test refactoring.


Hopefully caught them all this time.


Added test to ensure CollectionEquivalentConstraint returns a CollectionEquivalentConstraintResult.


Fixed some broken tests.


Add test to ensure that CollectionEquivalentConstraint makes use of new feature by default.


Added test files to all test projects.


Removed unnecessary include in csproj and removed unnecessary using statements in CollectionEquivalentConstraintResultTests.


Cleaned up some of the tests, added one more.


Added warning disable for linux builds.


Some cleaning up.


Rebased off of upstream/master, fixed one error after merging.
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.

4 participants