Codeberg/Community
54
325
Fork
You've already forked Community
12

Using No reply Address #618

Closed
opened 2022年05月08日 14:22:50 +02:00 by Ghost · 13 comments

In Github, I can use the No-Reply Address provided by them for GPG Key. But I can't use Codeberg's No-Reply address for the GPG key in my Codeberg account as it doesn't recognize it.

It would be great if Codeberg can also accept GPG keys of its own No-Reply Address.

I hope, I am clear in my Wording.

In Github, I can use the No-Reply Address provided by them for GPG Key. But I can't use Codeberg's No-Reply address for the GPG key in my Codeberg account as it doesn't recognize it. It would be great if Codeberg can also accept GPG keys of its own No-Reply Address. I hope, I am clear in my Wording.

In Github, I can use the No-Reply Address provided by them for GPG Key. But I can't use Codeberg's No-Reply address for the GPG key in my Codeberg account as it doesn't recognize it.

Do you mean adding a GPG-key to your account with the no-reply adress as the email?

Or perhabs you mean that commits won't be signed if you commit via the no-reply email address in the WebUI.

> In Github, I can use the No-Reply Address provided by them for GPG Key. But I can't use Codeberg's No-Reply address for the GPG key in my Codeberg account as it doesn't recognize it. > Do you mean adding a GPG-key to your account with the no-reply adress as the email? Or perhabs you mean that commits won't be signed if you commit via the no-reply email address in the WebUI.

@Gusted I mean the First, Adding GPG key with no-reply address as email.

@Gusted I mean the First, Adding GPG key with no-reply address as email.

So, Is it possible to do now or It must be also added to Gitea too ?

So, Is it possible to do now or It must be also added to Gitea too ?

It must be supported by Gitea.

It must be supported by Gitea.

So, This is reported to Gitea too or will be ?

I am eargerly waiting for this.

So, This is reported to Gitea too or will be ? I am eargerly waiting for this.

So, This is reported to Gitea too or will be ?

I am eargerly waiting for this.

It should be reported to Gitea to actually have this feature, feel free to do so.

> So, This is reported to Gitea too or will be ? > > I am eargerly waiting for this. It should be reported to Gitea to actually have this feature, feel free to do so.

I could do that. But I don't know where to.

I could do that. But I don't know where to.
Owner
Copy link

Gitea is developed at GitHub https://github.com/go-gitea/gitea/issues

If you don't have an account there, we can try to forward it, but this sometimes takes a moment, because it's hard to participate in many issue discussions at once ...

Gitea is developed at GitHub https://github.com/go-gitea/gitea/issues If you don't have an account there, we can try to forward it, but this sometimes takes a moment, because it's hard to participate in many issue discussions at once ...

I do have an account on Github. But, I don't want to do the same there and make a link between the Two. I just want these two Compartmentalized.

Please forward it there. I don't have any urgency.

I do have an account on Github. But, I don't want to do the same there and make a link between the Two. I just want these two Compartmentalized. Please forward it there. I don't have any urgency.

@Gusted I arrived here due to the second issue you suggest above:

Or perhabs you mean that commits won't be signed if you commit via the no-reply email address in the WebUI.

On GitHub, repos created via the WebUI with a GPG key attached to the account are signed, but that appears not to be the case on Codeberg? Any solution, or is that just how it is?

@Gusted I arrived here due to the second issue you suggest above: > Or perhabs you mean that commits won't be signed if you commit via the no-reply email address in the WebUI. On GitHub, repos created via the WebUI with a GPG key attached to the account are signed, but that appears not to be the case on Codeberg? Any solution, or is that just how it is?

On GitHub, repos created via the WebUI with a GPG key attached to the account are signed, but that appears not to be the case on Codeberg? Any solution, or is that just how it is?

Codeberg doesn't have that functionally enabled currently. I will ask if it's possible to enable it.

> On GitHub, repos created via the WebUI with a GPG key attached to the account are signed, but that appears not to be the case on Codeberg? Any solution, or is that just how it is? Codeberg doesn't have that functionally enabled currently. I will ask if it's possible to enable it.

Thanks for confirming! If it could be enabled, that would be cool, but I understand if there are constraints or limitations.

Thanks for confirming! If it could be enabled, that would be cool, but I understand if there are constraints or limitations.

So the original author is a Ghost, so not really see the fit to have the issue open.

@steinea please follow #400

So the original author is a Ghost, so not really see the fit to have the issue open. @steinea please follow #400
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#618
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

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?