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.

Sign up for GitHub

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

Jump to bottom

don't use branch name for badges #134

Merged
merged 1 commit into from
Feb 17, 2021
Merged

don't use branch name for badges #134

merged 1 commit into from
Feb 17, 2021

Conversation

azjezz
Copy link
Owner

@azjezz azjezz commented Feb 17, 2021

No description provided.

@azjezz azjezz added Status: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity labels Feb 17, 2021
@azjezz azjezz added this to the 1.4.0 milestone Feb 17, 2021
@azjezz azjezz self-assigned this Feb 17, 2021
@azjezz azjezz merged commit a48ed5c into 1.4.x Feb 17, 2021
@coveralls
Copy link

Pull Request Test Coverage Report for Build 576059234

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 99.958%
Totals Coverage Status
Change from base Build 576046752: 0.0%
Covered Lines: 2403
Relevant Lines: 2404
💛 - Coveralls

@azjezz azjezz deleted the fix/readme branch February 20, 2021 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@azjezz azjezz

Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity
Projects
None yet
Milestone
1.4.0
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@azjezz @coveralls