forgejo/forgejo

Fork 876

angelnu added the

enhancement/feature

label 2025年01月03日 14:01:14 +01:00

angelnu referenced this issue 2025年01月03日 14:38:41 +01:00

0ko added the

code/api

label 2025年01月03日 17:23:31 +01:00

Gusted referenced this issue from a commit 2025年01月05日 03:32:50 +01:00

Sign in to join this conversation.

No Branch/Tag specified

Clear labels

arch

riscv64

Archived

backport/v1.19

Scheduled for backport to Forgejo v1.19

Archived

backport/v1.20

Scheduled for backport to Forgejo v1.20

Archived

backport/v1.21/forgejo

Scheduled for backport to Forgejo v1.21

Archived

backport/v10.0/forgejo

Automated backport to v10.0

Archived

backport/v11.0/forgejo

Automated backport to v11.0

backport/v12.0/forgejo

Automated backport to v12.0

Archived

backport/v13.0/forgejo

Automated backport to v13.0

Archived

backport/v14.0/forgejo

Automated backport to v14.0

Archived

backport/v15.0/forgejo

Automated backport to v15.0

backport/v16.0/forgejo

Automated backport to v16.0

backport/v7.0/forgejo

Scheduled for backport to Forgejo v7.0

Archived

backport/v8.0/forgejo

Scheduled for backport to Forgejo v8.0

Archived

backport/v9.0/forgejo

Scheduled for backport to Forgejo v9.0

Archived

breaking

The release containing this change is not backward compatible

bug

Something is not working

Archived

bug

confirmed

it can be reproduced

bug

duplicate

bug has already been reported in the Forgejo tracker

bug

needs-more-info

the information provided does not contain enough details

bug

new-report

bug has just been reported and need triage (default label on issue creation)

bug

reported-upstream

bug cannot be fixed within Forgejo easily, it has been reported upstream

code/actions

Forgejo Actions feature

code/api

API

code/auth

Forgejo Authentication

code/auth/faidp

Forgejo as Identity Provider (in OAuth/OIDC flow)

code/auth/farp

Forgejo as Relying Party / Client (in OAuth/OIDC flow)

code/email

Everything related to email in Forgejo

code/federation

Federation

code/git

Related to the Git backend in Forgejo

code/migrations

Migration between Git forges (i.e. for GitHub, GitLab, Gitea, Forgejo, etc.). NOT for database migrations.

code/packages

Forgejo package and container registry

code/wiki

database

MySQL

https://www.mysql.com/

database

PostgreSQL

https://www.postgresql.org/

database

SQLite

https://sqlite.org/

dependency-upgrade

https://codeberg.org/forgejo/forgejo/issues/2779

dependency

Chi

https://github.com/go-chi/chi/

Archived

dependency

Chroma

https://github.com/alecthomas/chroma/

Archived

dependency

F3

https://f3.forgefriends.org/

dependency

ForgeFed

https://forgefed.org

dependency

garage

https://git.deuxfleurs.fr/Deuxfleurs/garage

dependency

Gitea

https://github.com/go-gitea/gitea

Archived

dependency

Golang

https://go.dev/

Discussion

duplicate

This issue or pull request already exists

enhancement/feature

New feature

forgejo/accessibility

Accessibility (a11y)

forgejo/branding

Branding (logo, name, tagline etc.)

forgejo/ci

Forgejo Actions CI configuration

forgejo/commit-graph

The commit graph feature and page.

forgejo/documentation

forgejo/furnace cleanup

Keeping Forgejo in sync with its dependencies and contributing back to them

Archived

forgejo/i18n

t9n/translation, l10n/localization, and i18n/internationalization of Forgejo

forgejo/interop

Interoperability with other services: Webhooks, bridges, integrations

forgejo/moderation

Moderation

forgejo/privacy

Privacy first

forgejo/release

Release management

forgejo/scaling

Performance and scaling

forgejo/security

Security (please disclose responsibly)

forgejo/ui

User interface

Gain

High

User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.

Gain

Nice to have

This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.

Gain

Undefined

Not enough information to assess the request's benefits. This issue may be closed if no gain is established: You can help by giving us more input.

Gain

Very High

User research indicates that this is an important improvement for Forgejo users. Contributions very welcome!

good first issue

Optimal for first-timers! Make sure to look for further explanations and ask for help if needed. If you want, you can consider the person who added this label as a point of contact.

i18n/backport-stable

This PR needs to be backported to stable branch of Forgejo safely and manually, using a migration script.

impact

large

Large impact: Potential data loss, many users affected, major degradation in UX.

impact

medium

Medium impact: Several users affected, degradation in UX, workarounds might be available but inconvenient.

impact

small

Small impact: No data loss, workarounds might be available, affects few users.

impact

unknown

Report was not yet triaged to assess impact.

Incompatible license

This pull request contains changes that are not (yet) compatible with the current Forgejo license

issue

closed

The issue was resolved in the repository of the dependency

issue

do-not-exist-yet

An issue should be created in the respository of the dependency

issue

open

An open issue exists in the upstream repository of the dependency

manual test

Pull requests that have been merged with a manual test

Archived

Manually tested during feature freeze

The manual test instructions were followed

OS

FreeBSD

Specific to the FreeBSD Operating System

OS

Linux

Specific to (GNU/)Linux Operating Systems

OS

macOS

Specific to the MacOS Operating System

OS

Windows

Specific to the Windows Operating System

problem

A user report about a problem. Needs to be triaged to find potential solutions.

QA

regression

found in the version of the milestone and not before

release blocker

Issues that must be fixed before the release can be published

Release Cycle

Feature Freeze

Only bug fixes with automated tests (except for CSS/JavaScript)

release-blocker

v7.0

Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024

Archived

release-blocker

v7.0.1

Issues that must be fixed before Forgejo v7.0.1 can be released

Archived

release-blocker

v7.0.2

Issues that must be fixed before Forgejo v7.0.2 can be released

Archived

release-blocker

v7.0.3

Issues that must be fixed before Forgejo v7.0.3 can be released

Archived

release-blocker

v7.0.4

Issues that must be fixed before Forgejo v7.0.4 can be released

Archived

release-blocker

v8.0.0

Issues that must be fixed before Forgejo v8.0.0 can be released

Archived

release-blocker/v9.0.0

Issues that must be fixed before Forgejo v9.0.0 can be released

Archived

run-all-playwright-tests

Add this label to a PR to run all playwright tests manually.

run-end-to-end-tests

Trigger additional tests on the PR when it is ready to be merged

stage

2-research

Needs research to moe on.

stage

3-design

Needs design to move on

stage

4-implementation

This is actionable and waits for implementation

test

manual

manual testing has been documented

test

needed

test should be added

test

needs-help

help needed to add a test

test

not-needed

no additional test is needed

test

present

test has been added

untested

Pull requests that have been merged with no test and submitted as is to the dependency where they belong

Archived

User research - time-tracker

Time tracking feature for issues and the JS stopwatch.

valuable code

This PR was closed because the implementation is incomplete

worth a release-note

Add this PR to the release notes

User research - Accessibility

Requires input about accessibility features, likely involves user testing.

User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.

User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.

User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.

User research - Errors

How to deal with errors in the application and write helpful error messages.

User research - Filters

How filter and search is being worked with.

User research - Future backlog

The issue might be inspiring for future design work.

User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc

User research - Labels

Active research about Labels

User research - Moderation

Moderation Featuers for Admins are undergoing active User Research

User research - Needs input

Use this label to let the User Research team know their input is requested.

User research - Notifications/Dashboard

Research on how users should know what to do next.

User research - Rendering

Text rendering, markup languages etc

User research - Repo creation

Active research about the New Repo dialog.

User research - Repo units

The repo sections, disabling them and the "Add more" button.

User research - Security

User research - Settings (in-app)

How to structure in-app settings in the future?

Milestone

No milestone

Subscribe

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".