Update readme #185
No reviewers
Labels
No Label
has/backport
has/pull
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
No Milestone
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#185
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "lunny:lunny/update_readme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As title.
@ -17,3 +17,3 @@
## Authors
* [Maintainers](https://github.com/orgs/go-gitea/people)
* [Maintainers](https://gitea.com/org/gitea/members)
Same comment as other PR, this would need to wait until Gitea can show these pages publicly
blocked by https://github.com/go-gitea/gitea/issues/7501
@lunny if we split this PR into two we can fix badge at readme
@6543 Could you help to do that?
Firt change is now part of #193
@lunny this change can be removed ... or rebase this PR ...
For the record: I'm not watching this repo, nor I am subscribed to this issue (while I'm writing this) but I still receive email notifications.
@strk please fire an issue on gitea.
@strk I think you're receiving mails because you're member of the Gitea organization. Maybe you can adjust your notification settings at https://gitea.com/user/settings/account .
@strk you are not subscribed but you are a participant because you approved. I agree that you should be able to unsubscribe, though, which you currently can't.
@guillep2k currently you cant unsubscribe from a specific issue explisit ... I'm on this, so this might change ...
I'll close this since the only change left is about org-member-page ... witch has its own issue on github ...
Pull request closed