Skip to content

Update sequence_provider.rst #10948

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

Closed
wants to merge 2 commits into from
Closed

Conversation

DonCallisto
Copy link
Contributor

I think that is better to explain this difference as someone could misunderstand and think that a group in the sequence, alone, will trigger the validation of all groups in the sequence.

I think that is better to explain this difference as someone could misunderstand and think that a group in the sequence, alone, will trigger the validation of all groups in the sequence.
Copy link
Contributor

@HeahDude HeahDude left a comment

Choose a reason for hiding this comment

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

Thank you for submitting this PR.

@HeahDude HeahDude added this to the 3.4 milestone Feb 4, 2019
@javiereguiluz
Copy link
Member

Thank you Samuele.

javiereguiluz added a commit that referenced this pull request Feb 8, 2019
This PR was submitted for the master branch but it was squashed and merged into the 3.4 branch instead (closes #10948).

Discussion
----------

Update sequence_provider.rst

I think that is better to explain this difference as someone could misunderstand and think that a group in the sequence, alone, will trigger the validation of all groups in the sequence.

Commits
-------

7f5d9c3 Update sequence_provider.rst
@DonCallisto
Copy link
Contributor Author

Why is this closed and not merged @javiereguiluz? 🤔

@DonCallisto
Copy link
Contributor Author

Oh, sorry, I've seen only now you referenced this in another commit.

@javiereguiluz
Copy link
Member

@DonCallisto we use a proprietary tool to merge things. Since we changed the branch while merging (to merge this in 3.4 instead of master) GitHub makes it look "closed" instead of "merged", but it's merged :)

We're sorry for the confusion, but I prefer to do things like rebasing myself when merging to not bother contributors. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants