mirror of
https://github.com/lupyuen/lupyuen.github.io.git
synced 2025-01-12 22:38:31 +08:00
Discussion on __GitHub Coexistence__
This commit is contained in:
parent
89955d3851
commit
1f955f2fd8
1 changed files with 4 additions and 0 deletions
|
@ -131,6 +131,8 @@ Indeed, we'll probably call [__GitHub API__](https://lupyuen.github.io/articles/
|
|||
|
||||
With this setup, we can't allow Pull Requests to be locally merged at Forgejo. Instead, Pull Requests shall be __merged at GitHub__. Then Forgejo shall auto-sync the updates into our Git Forge.
|
||||
|
||||
[(Discussion on __GitHub Coexistence__)](https://lists.apache.org/thread/mphcf71f9xywgd1rvcsllp2klv606m87)
|
||||
|
||||
That's why we need __Two Mirror Repos__: Read-Only and Read-Write...
|
||||
|
||||
| | |
|
||||
|
@ -313,6 +315,8 @@ We'll probably call [__GitHub API__](https://lupyuen.github.io/articles/llm#call
|
|||
|
||||
Right now we can't allow Pull Requests to be locally merged at Forgejo. Instead, we'll merge Pull Requests at GitHub. Then wait for Forgejo to auto-sync the updates back into our Git Forge.
|
||||
|
||||
[(Discussion on __GitHub Coexistence__)](https://lists.apache.org/thread/mphcf71f9xywgd1rvcsllp2klv606m87)
|
||||
|
||||
Which explains why we need __Two Mirror Repos__: Read-Only Mirror and Read-Write Mirror.
|
||||
|
||||
| | |
|
||||
|
|
Loading…
Reference in a new issue