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

Enhance release list #6025

Merged
merged 33 commits into from
Oct 22, 2020
Merged

Conversation

adelowo
Copy link
Member

@adelowo adelowo commented Feb 9, 2019

  • If the email of the tag commit belongs to a user, make the user the publisher else do nothing ( current behavior)
  • For tags pushed to Gitea, show the number of commits behind the master branch - as is done for releases created via the UI

screenshot 2019-02-09 at 15 57 08

@codecov-io
Copy link

codecov-io commented Feb 9, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@eb4c10d). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #6025   +/-   ##
=========================================
  Coverage          ?   41.26%           
=========================================
  Files             ?      570           
  Lines             ?    74398           
  Branches          ?        0           
=========================================
  Hits              ?    30703           
  Misses            ?    39868           
  Partials          ?     3827

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 eb4c10d...19a6d50. Read the comment docs.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Feb 9, 2019
@lafriks lafriks added the type/enhancement An improvement of existing functionality label Feb 9, 2019
models/release.go Outdated Show resolved Hide resolved
@techknowlogick techknowlogick added this to the 1.9.0 milestone Feb 11, 2019
@MarkusAmshove
Copy link
Contributor

Does "commits behind" default to master or default branch? The latter would be better IMO :-)

@adelowo
Copy link
Member Author

adelowo commented Feb 11, 2019

It defaults to the default branch

Also show the number of commits behind the default branch for tags created outside the UI

don't show the tag date again for tags pushed to the repo. Since it is already on the sidebar and looks like duplication
@adelowo
Copy link
Member Author

adelowo commented Mar 28, 2019

Ready for review :)

models/migrations/v83.go Outdated Show resolved Hide resolved
models/migrations/v83.go Outdated Show resolved Hide resolved
Copy link
Member

@kolaente kolaente left a comment

Choose a reason for hiding this comment

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

Please resolve conflicts, looks good otherwise.

@techknowlogick techknowlogick modified the milestones: 1.9.0, 1.10.0 Jun 4, 2019
@stale
Copy link

stale bot commented Aug 4, 2019

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions.

@stale stale bot added the issue/stale label Aug 4, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Aug 4, 2019
@stale stale bot removed the issue/stale label Aug 4, 2019
@lunny lunny modified the milestones: 1.10.0, 1.11.0 Sep 15, 2019
@lunny
Copy link
Member

lunny commented Nov 16, 2019

Please resolve the conflicts.

1 similar comment
@lunny
Copy link
Member

lunny commented Dec 14, 2019

Please resolve the conflicts.

@adelowo
Copy link
Member Author

adelowo commented Dec 14, 2019

Will do this weekend

Copy link
Contributor

@zeripath zeripath left a comment

Choose a reason for hiding this comment

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

Gitrepos aren't always closed if there is an error. You must ensure that they're closed.

@lunny lunny modified the milestones: 1.13.0, 1.14.0 Sep 10, 2020
@richmahn
Copy link
Contributor

@adelowo Looks like we have conflicts again, and the defer issue mentioned above.

@codecov-io
Copy link

codecov-io commented Oct 15, 2020

Codecov Report

Merging #6025 into master will decrease coverage by 0.04%.
The diff coverage is 4.81%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6025      +/-   ##
==========================================
- Coverage   42.21%   42.17%   -0.05%     
==========================================
  Files         683      684       +1     
  Lines       75458    75541      +83     
==========================================
+ Hits        31858    31860       +2     
- Misses      38377    38456      +79     
- Partials     5223     5225       +2     
Impacted Files Coverage Δ
models/migrations/migrations.go 2.44% <ø> (ø)
models/migrations/v156.go 0.00% <0.00%> (ø)
routers/repo/release.go 26.72% <100.00%> (+0.31%) ⬆️
services/release/release.go 31.31% <100.00%> (+2.14%) ⬆️
modules/util/timer.go 42.85% <0.00%> (-42.86%) ⬇️
modules/queue/unique_queue_disk_channel.go 53.84% <0.00%> (-1.54%) ⬇️
modules/queue/workerpool.go 59.18% <0.00%> (-0.82%) ⬇️
services/pull/check.go 48.90% <0.00%> (-0.73%) ⬇️
services/pull/pull.go 40.78% <0.00%> (ø)
... and 2 more

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 9658610...4d85686. Read the comment docs.

@adelowo
Copy link
Member Author

adelowo commented Oct 15, 2020

Ready for review

models/migrations/v156.go Outdated Show resolved Hide resolved
models/migrations/v156.go Outdated Show resolved Hide resolved
@zeripath
Copy link
Contributor

@lunny would you like to re-review?

@techknowlogick
Copy link
Member

🚀

@techknowlogick techknowlogick merged commit e918636 into go-gitea:master Oct 22, 2020
@lunny
Copy link
Member

lunny commented Oct 22, 2020

@zeripath Sorry I missed this PR, I send another PR, please see #13254 .

@6543 6543 deleted the enhance_release_list branch October 22, 2020 09:50
continue
}

release.PublisherID = u.ID
Copy link
Member

Choose a reason for hiding this comment

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

This maybe override the original PublisherID, @adelowo why we need that?

@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.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.