Skip to content
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

Merge two config into recommended config #155

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

bmish
Copy link
Member

@bmish bmish commented Feb 23, 2021

This can be merged as part of the V6 release: #114.

It would be easiest if we merged some other changes first then rebased this PR:

Sorry, something went wrong.

@bmish bmish force-pushed the recommended-merge-two-config branch from 050e156 to 8d00e31 Compare February 23, 2021 17:48
@coveralls
Copy link

coveralls commented Feb 23, 2021

Coverage Status

Coverage remained the same at 100.0% when pulling 80dd185 on bmish:recommended-merge-two-config into 335fc8c on platinumazure:master.

@bmish bmish force-pushed the recommended-merge-two-config branch from 8d00e31 to 42715d2 Compare February 23, 2021 17:54
@bmish
Copy link
Member Author

bmish commented Mar 15, 2021

I'll rebase this in one minute...

@platinumazure
Copy link
Collaborator

Hi @bmish, looks like there are now conflicts, mind rebasing on or merging master? Thanks!

@bmish bmish force-pushed the recommended-merge-two-config branch from ed2cc60 to 80dd185 Compare March 15, 2021 01:41
@bmish
Copy link
Member Author

bmish commented Mar 15, 2021

Can you merge #157 first? Then I'll need to rebase this PR again after that.

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

Successfully merging this pull request may close these issues.

None yet

3 participants