[x] Indicade if it is merged manualy (https://github.com/go-gitea/gitea/issues/7976) (https://github.com/go-gitea/gitea/pull/8449)
[ ] fix restore button (https://github.com/go-gitea/gitea/issues/7569)
[x] del button should be hidden on an archived repository (https://github.com/go-gitea/gitea/issues/7653)
[ ] put all controll buttons in the same td
and make them look similar (https://github.com/go-gitea/gitea/issues/7606)
perhaps the other information is alo usefull (the tags, the commits behind/ahead) ...
This has been merged in #6990
Something are absent.
@lunny #6990 would resolve my needs - i searched for it but didn't found it - sory
Something are absent ...
shoud we rename the issue to specify it?
@6543 title changed
Sounds like a good idea. I'll see if I can work on this.
Something are absent.
time
Isn't time already there?
@gary-kim Oh. yes, time is already there.
@gary-kim thanks! update issue tasks
what do you think should it say merged when latest commit is in some other branch or if it is in default one?
@lunny @gary-kim @techknowlogick
partially fixed by #7461
@6543 merged to which branch? Default branch?
@lunny
I think we dont need souch lable like merged, do we?
and remove corner of menue?!?
@6543 If a repository use pull request, the merged label is unusable. But for others with no pull request, merged label is very usable. I will find time to review your PR.
https://github.com/go-gitea/gitea/pull/7520 is now ready to review (again [css moved])
Current State: https://github.com/go-gitea/gitea/pull/7520#issuecomment-513991651 of Download Button
@lunny @gary-kim what do you think of PR 7520 curent state?
@6543 I have gave that L-G-T-M
@6543 I have gave that L-G-T-M
@lunny i split the PR to get things that are right merged and work only on things wich need improvement - I'm sorry to bother you with this [again].
updated tasks list
@6543 added https://github.com/go-gitea/gitea/issues/7653 on task list
@6543 added #7653 on task list
ok this one line i could realy add to PR 7604 but i dont get it because it was realy out of topic ...
I will be on a trip for a month, so I'm not mad when someone else does tasks :)
@6543 Thanks for your work. Have a good time!
@lunny
@6543 If a repository use pull request, the merged label is unusable. But for others with no pull request, merged label is very usable. I will find time to review your PR.
so if the last commit is includet in default branch and folowing commit on default branch has a message wich *[Mm]erge*<branch name>*
then it is merged manualy and the merge flag sould also aperar?
is that what you mean?
and showing "New Pull Request" Button if there is nothing to merge is noncese (latest commit is included in default branch ...). if you click on it next page tells you: "These branches are equal. There is no need to create a pull request."
@6543 good catch
https://github.com/go-gitea/gitea/pull/7977 is ready to merge :D
and https://github.com/go-gitea/gitea/issues/7976 is way more complicated ...
@lunny have a look at the PR(https://github.com/go-gitea/gitea/pull/7979)?
Reverence PR https://github.com/go-gitea/gitea/pull/8449 -> a other todo will be checked soon
so it's time I'll close this huge one
lot of things work now ...
Thanks to al who helped me ...
Most helpful comment
@6543 I have gave that L-G-T-M