Skip to content

Explanation for missing releases #3823

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
Merged
merged 1 commit into from
Apr 21, 2018
Merged

Explanation for missing releases #3823

merged 1 commit into from
Apr 21, 2018

Conversation

HoffmannP
Copy link
Contributor

@HoffmannP HoffmannP commented Apr 20, 2018 •
edited by lafriks
Loading

Searched for missing releases/tags for some time, thought the solution might be helpful to others

@HoffmannP
Explanation for missing releases
91bde07 
Searched for missing releases/tags for some time, thought the solution might be helpful to others
@codecov-io
Copy link

Codecov Report

Merging #3823 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3823   +/-   ##
=======================================
  Coverage   23.02%   23.02%           
=======================================
  Files         126      126           
  Lines       24894    24894           
=======================================
  Hits         5731     5731           
  Misses      18287    18287           
  Partials      876      876

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 725835b...91bde07. Read the comment docs.

@bkcsoft bkcsoft added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 20, 2018
@lafriks lafriks added the type/docs This PR mainly updates/creates documentation label Apr 20, 2018
@thehowl
Copy link
Contributor

thehowl commented Apr 20, 2018

This seems more like a general git issue rather than a Gitea issue, but ok, LGTM.

@bkcsoft bkcsoft added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Apr 20, 2018
@lunny lunny added this to the 1.5.0 milestone Apr 21, 2018
@lunny
Copy link
Member

lunny commented Apr 21, 2018

LGTM

@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 21, 2018
@lunny lunny merged commit 48b19a5 into go-gitea:master Apr 21, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/docs This PR mainly updates/creates documentation
Projects
None yet
Milestone
1.5.0
Development

Successfully merging this pull request may close these issues.
6 participants
@HoffmannP @codecov-io @thehowl @lunny @lafriks @bkcsoft