Is it possible that the Link to an new issue and the first sentence will be published via activity pub to mastodon?
Publishing Issues via Activity Pub #397
gitea is realy interested in ForgeFed ... witch is based on ActivityPub ... so it should be posible if https://github.com/go-gitea/gitea/issues/14186 got implemented ...
the easyest way for now would be to use webhooks + bot ...
Note that there's a new project FedeProxy that may also provide such functionality, and will (probably) be independent of any forges by acting as a bridge / mediator. They are also considering ForgeFed support.
Also note that there are probably easier ways to implement this than having the full gitea#14186, i.e. similar to projects that provide simple AP bridges (I maintain that watchlist), or WP integrations. Nothing implemented in Go language yet, though.
well there could be a bridge first ... the goal is to get gitea speak Federated :D
( Just a FYI: Fedeproxy has obtained funding, and are bootstrapping their project. They are looking to do User research first, and seeking for experiences of people that do not use Github. More info: https://forum.fedeproxy.eu/ )
Nice. Are you talking of this thread? https://forum.fedeproxy.eu/t/call-to-developers-without-a-github-account/75/4
Yes, and there is also the prep topic with background info: https://forum.fedeproxy.eu/t/preparing-the-user-research/71
User Research is indeed in progress, and it would be great to hear from people who do not have a GitHub account and struggle to contribute to Free Software projects because of that. I told my own story but I'm a little biased :-)
closing for #683
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
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.
Things related to Codeberg's external communication
More information is needed
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.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
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?