feat: recognize Forgejo and Gitea provider configuration#266
Conversation
|
This change is part of the following stack:
Change managed by git-spice. |
roborev: Combined Review (
|
roborev: Combined Review (
|
ba45b96 to
d62e56b
Compare
aa08bfb to
5487890
Compare
roborev: Combined Review (
|
5487890 to
0f40d24
Compare
roborev: Combined Review (
|
0f40d24 to
1d79f4f
Compare
roborev: Combined Review (
|
6adcc34 to
bd49b2f
Compare
1d79f4f to
535775a
Compare
roborev: Combined Review (
|
bd49b2f to
df23946
Compare
535775a to
3b4fa7d
Compare
roborev: Combined Review (
|
df23946 to
075d13d
Compare
3b4fa7d to
f978956
Compare
075d13d to
db7ad6b
Compare
roborev: Combined Review (
|
f978956 to
0141271
Compare
db7ad6b to
9c77d8e
Compare
0141271 to
2d74966
Compare
Adds Forgejo and Gitea metadata and config parsing so Codeberg, Gitea.com, and self-hosted repos can be represented before provider sync is implemented.
Include provider default token env vars in the runtime sanitizer even when a repo-specific token_env is configured, because token resolution can still fall back to public Forgejo/Gitea defaults when the repo env var is empty.
2d74966 to
7a25f7d
Compare
Adds Forgejo and Gitea metadata and config parsing so Codeberg, Gitea.com, and self-hosted repos can be represented before provider sync is implemented.