Gitea: Functionality that is useful for Gitea's administrative workflow

[guillep2k]

As the move to gitea.com is getting closer, I was thinking about those useful features that we as maintainers will miss after we move; I mean those specifically needed for the workflow of maintaining Gitea itself.

The idea is to make a list of those features we consider the most useful, so contributors can have specific goals to help with.

As a maintainer I'm not familiar with many of the tasks involved in the administration of Gitea, so I'll start with my short list to open the discussion.

NOTE: in this list I'm collecting ideas from the comments below

• [x] An Update branch button #9750 (#9784).
• [ ] Select specific commits when reviewing code.
• [x] Expand/collapse source files while reviewing code #8579 (#8924).
• [x] The ability to expand code beyond the given context when comparing/reviewing (#8924).
• [ ] Mark files as seen while reviewing code.
• [x] Close/reopen issues from PR comments (#8866).
• [x] Make changelog tool use Gitea (gitea/changelog#19).
• [ ] Show on Pull request list page:
  
  
  
  • [x] Number of required approvals still remaining, or the number approvals obtained (#8762) (#9274) (#10238).
  
  
  • [x] Has the PR passed CI.
  
  
  • [ ] Is it blocked by another issue/PR.
  
  
  • [x] Does it contain conflicts (#10130).
  
  
• [ ] Commiteable code change suggestions (beware non-utf8 encodings!); related: #9388.
• [x] Require branches to be up to date before merging #9786 (#11012).

Extra points

• [ ] Always display the members page for public organizations; see #7501

[davidsvantesson]

• [ ] A count of approvals in the PR page.

You already have that?
_This Pull Request doesn't have enough approvals yet. 1 of 2 approvals granted._
Or do you mean the list of reviewers in the right sidebar? That I think would be useful to have.

[zeripath]

He means on the list of PRs page. In GitHub we use labels to set this but Gitea has that built in

[lunny]

It could be `Show approvals counts on Pull request list page"

[guillep2k]

For this one:

• [ ] Does it produce conflicts.

I think a small client-side button to check could be used? I mean, it could show something like ❔ that, when pressed, a request is sent to the server and the button is changed into ✔️ or ❌.

[blueworrybear]

It's better to add Expand Up and Expand Down button too IMO. 🤔

[guillep2k]

It's better to add Expand Up and Expand Down button too IMO. 🤔

Sorry, are you referring to the "does it produce conflicts" option?

[jolheiser]

Suggestions! 😢
(Meaning the ones you can commit)

[jamesorlakin]

Number of required approvals still remaining, or the number approvals obtained.

I came across this issue seeing if this exact feature was possibly in progress already, or whether it was worth me having an attempt. I've never touched Go before (I'm a full-stack TypeScript dev) but love the work put into Gitea!

After some playing about for over an hour I have this:

The first number being the number of granted approvals, and the second the required ones. Let me know if you would be interested in a PR 👍 .

[lafriks]

@jamesorlakin sure send PR ;)

[jamesorlakin]

@lafriks Sure thing, I'll try to get it out tomorrow

[blueworrybear]

@guillep2k
I mean the code folding/unfolding. Here is an example:

[guillep2k]

@guillep2k
I mean the code folding/unfolding. Here is an example:

Oh, of course!

[jolheiser]

Changelog tool now supports Gitea. 🎉

[jamesorlakin]

• [ ] Does it produce conflicts. _(Much harder, probably)_

Would this just mean making use of the ConflictedFiles array on the pull model? If so, I whipped up this in a few lines by tweaking the template:

[guillep2k]

Would this just mean making use of the ConflictedFiles array on the pull model? If so, I whipped up this in a few lines by tweaking the template:

@jamesorlakin Care to submit a PR? 😁

[lunny]

It seems it's easier to diaplsy files conflicted.

[zeripath]

This is on the PRs list page not on a particular pr page.

[6543]

@guillep2k you can add #11012

[6543]

@guillep2k you can check Require branches to be up to date before merging by the way :)