Item 5 of the console proposal. The console no longer merges upstream,
but new upstream versions are still read for features worth writing
here, and this makes that automatic, like inbuxa-server's own
upstream-watch.
.gitea/workflows/upstream-watch.yml runs daily at 06:47 UTC, or by
hand. For each upstream web UI version tagged since the fork point
(v1.0.11), it opens one "Review upstream web UI vX" issue, compared with
the version before it.
Files grouped by license header. Each issue lists the changed
files under: Enterprise only (never open), Dual holding Enterprise
snippets (never open), Removed, Dual (may be read), No license header
(check before reading).
Metadata only. It reads tags and the compare from GitHub's API,
plus each changed file's license lines. No upstream code goes into
the issue, only paths, change counts and licenses, and no upstream
project name.
Tags, not releases, since upstream has tagged versions before
publishing them as releases.
One issue per version. An existing issue with the same title,
open or closed, stops a second.
Checked locally with DRY_RUN=1, using the workflow's own script:
With the real fork point it reports nothing new; upstream's v2.0.0
isn't tagged yet.
With the fork point moved back to v1.0.9, it builds the v1.0.10 and
v1.0.11 issues correctly.
The license classifier was tested on made-up Enterprise-only,
snippet, dual, MIT and headerless files.
No new strings.
Item 5 of the console proposal. The console no longer merges upstream,
but new upstream versions are still read for features worth writing
here, and this makes that automatic, like inbuxa-server's own
upstream-watch.
`.gitea/workflows/upstream-watch.yml` runs daily at 06:47 UTC, or by
hand. For each upstream web UI version tagged since the fork point
(v1.0.11), it opens one "Review upstream web UI vX" issue, compared with
the version before it.
- **Files grouped by license header.** Each issue lists the changed
files under: Enterprise only (never open), Dual holding Enterprise
snippets (never open), Removed, Dual (may be read), No license header
(check before reading).
- **Metadata only.** It reads tags and the compare from GitHub's API,
plus each changed file's license lines. No upstream code goes into
the issue, only paths, change counts and licenses, and no upstream
project name.
- **Tags, not releases,** since upstream has tagged versions before
publishing them as releases.
- **One issue per version.** An existing issue with the same title,
open or closed, stops a second.
Checked locally with `DRY_RUN=1`, using the workflow's own script:
- With the real fork point it reports nothing new; upstream's v2.0.0
isn't tagged yet.
- With the fork point moved back to v1.0.9, it builds the v1.0.10 and
v1.0.11 issues correctly.
- The license classifier was tested on made-up Enterprise-only,
snippet, dual, MIT and headerless files.
No new strings.
The console no longer merges upstream, but new upstream versions are
still read for features worth writing here. A daily job (06:47 UTC, or
by hand) opens a "Review upstream web UI vX" issue for each version
tagged since the fork point, v1.0.11, compared with the one before it.
The issue lists the changed files grouped by license header, so a
reader knows which may be opened: Enterprise-only files and files with
Enterprise snippets are named but marked never open. Only metadata is
read: tags and the compare from GitHub's API, and each changed file's
license lines. No upstream code goes into the issue, only paths, change
counts and licenses. Tags rather than releases, since upstream has
tagged versions before releasing them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Item 5 of the console proposal. The console no longer merges upstream,
but new upstream versions are still read for features worth writing
here, and this makes that automatic, like inbuxa-server's own
upstream-watch.
.gitea/workflows/upstream-watch.ymlruns daily at 06:47 UTC, or byhand. For each upstream web UI version tagged since the fork point
(v1.0.11), it opens one "Review upstream web UI vX" issue, compared with
the version before it.
files under: Enterprise only (never open), Dual holding Enterprise
snippets (never open), Removed, Dual (may be read), No license header
(check before reading).
plus each changed file's license lines. No upstream code goes into
the issue, only paths, change counts and licenses, and no upstream
project name.
publishing them as releases.
open or closed, stops a second.
Checked locally with
DRY_RUN=1, using the workflow's own script:isn't tagged yet.
v1.0.11 issues correctly.
snippet, dual, MIT and headerless files.
No new strings.