forgejo/docs
32
45
Fork
You've already forked docs
204

List available mirrored actions on data.forgejo.org #1287

Open
opened 2025年07月09日 18:59:33 +02:00 by mahlzahn · 1 comment

How

Using the git-mirror.yaml or https://git-mirror.forgejo.org/, we can extract all available actions on data.forgejo.org, and add them in a nicely formatted list, e.g. in docs/user/actions/forgejo-hosted.md.

Implementation

  1. workflow on /forgejo/k8s-cluster:
    needs write access to docs
    can run on push to main
  2. workflow on /forgejo/docs:
    needs to write only to self
    needs to be triggered, but can do with cron, e.g. once a day

Expected output

  • list of all actions with links to mirror, or
  • table with additional information, e.g. last update, latest version, what it does?, etc. – requires to scan through all git mirrors.

Alternatives

Create a landing page for data.forgejo.org with this information.

forgejo/discussions#365

### How Using the [`git-mirror.yaml`](https://codeberg.org/forgejo/k8s-cluster/src/branch/main/flux/apps/forgejo-code/git-mirror.yaml) or https://git-mirror.forgejo.org/, we can extract all available actions on data.forgejo.org, and add them in a nicely formatted list, e.g. in [[docs/user/actions/forgejo-hosted.md]]. ### Implementation 1. workflow on [[/forgejo/k8s-cluster]]: ➖ needs write access to docs ➕ can run on push to main 2. workflow on [[/forgejo/docs]]: ➕ needs to write only to self ➖ needs to be triggered, but can do with cron, e.g. once a day ### Expected output - list of all actions with links to mirror, or - table with additional information, e.g. last update, latest version, what it does?, etc. – requires to scan through all git mirrors. ### Alternatives Create a landing page for data.forgejo.org with this information. ### Related forgejo/discussions#365
Contributor
Copy link

I favor 2. because it would only need to read git-mirror.yaml.

Although it is rather trivial, it may be useful to have a look at the shell script (and the associated tests) called to act on URLs to be mirrored.

I favor 2. because it would only need to read [`git-mirror.yaml`](https://codeberg.org/forgejo/k8s-cluster/src/commit/a47b43ac01b8d37b9854e031730bca3fb59f9610/flux/apps/forgejo-code/git-mirror.yaml). Although it is rather trivial, it may be useful to have a look at the [shell script](https://codeberg.org/forgejo/k8s-cluster/src/commit/a47b43ac01b8d37b9854e031730bca3fb59f9610/flux/apps/charts/git-mirror/git-mirror.sh) (and the [associated tests](https://codeberg.org/forgejo/k8s-cluster/src/commit/a47b43ac01b8d37b9854e031730bca3fb59f9610/flux/apps/charts/git-mirror/git-mirror-test.sh)) called [to act on URLs to be mirrored](https://codeberg.org/forgejo/k8s-cluster/src/commit/a47b43ac01b8d37b9854e031730bca3fb59f9610/flux/apps/charts/git-mirror/templates/cronjob.yaml#L20).
Sign in to join this conversation.
No Branch/Tag specified
next
v14.0
cli
v13.0
v11.0
v12.0
bp-v12.0-a6c8557
v7.0
v10.0
v9.0
v8.0
v1.21
v1.20
v1.19
v13.0.0-dev
Labels
Clear labels
404

Broken links or missing content
backport/v1.19

Changes which should be backported to the v1.19 docs

Archived

backport/v1.20

Changes which should be backported to the v1.20 docs

Archived

backport/v1.21

Changes which should be backported to the v1.21 docs

Archived

backport/v10.0

Automated backport to v10.0

Archived

backport/v11.0

Automated backport to v11.0
backport/v12.0

Automated backport to v12.0

Archived

backport/v13.0

Automated backport to v13.0
backport/v14.0

Automated backport to v14.0
backport/v7.0

Automated backport to the v7.0 docs

Archived

backport/v8.0

Automated backport to the v8.0 docs

Archived

backport/v9.0

Automated backport to the v9.0 docs

Archived

good first issue

This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta

Tooling and processes for maintaining the docs
new docs

Content to be added to the documentation

Archived

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
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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
forgejo/docs#1287
Reference in a new issue
forgejo/docs
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?