You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> ### Update Notice: Support for Syncing forks with upstream repo: [READ MORE]()
18
+
19
+
---
21
20
22
21
## Get Started.
23
-
<!--
24
-
> [!IMPORTANT]
25
-
> Failing to download msojocs server for all FE versions (Because msojocs renamed `master` branch to `main`), is fixed now
26
-
27
-
> [!IMPORTANT]
28
-
> Failing to download Yukihana Patch for FE versions < 5.17.0 (Because file names sctill contains `yukihana` not `yui` except `Yui-Patch 1.1.3 +`), is fixed now..
29
-
30
-
> [!IMPORTANT]
31
-
> Failing to download Yui Patch for all FE versions (Because the organization and repo-name renamed from `Yukihana` `--><!--` `Yui`), is fixed now.
32
-
<!--
33
-
> [!IMPORTANT]
34
-
> Failing to download Yukihana Patch for 5.17.0 + (Because continuous release & latest release didn't contain windows patches), is fixed now.
35
-
36
-
> [!IMPORTANT]
37
-
> Not patching 5.17.0+ when you trigger from "Custom Version - Workflow Dispatch" is Fixed now!
38
-
-->
39
22
> [!TIP]
40
-
> You must always check if your fork is up to date so no fails.
41
-
<!--
42
-
> [!NOTE]
43
-
> Only for Windows!
44
-
-->
23
+
> You must always check if your fork is up to date so no fails. (We reccomend you enable [0scheduled upstream pulling]())
24
+
45
25
* How even this Automated Patching Works?
46
26
- Well, this automated patch do the same that you do mannually for patching. It downloads fiddler everywhere extract it. Remove, Replace, Edit, Move files and then, the patched application is ready.
47
27
@@ -53,6 +33,7 @@ This's the guide for applying patch automatically.
53
33
> We highly reccomend you to use ***Latest Version - Workflow Dispatch***, which patch the latest available version.
54
34
> ***Custon Version - Workflow Dispatch*** allows you to select a version starting from 5.9.0 + too.
> - For this upstream pulling action to work, you need to enable [Upstream Sync](.github/workflows/cp_pull_upstream.yml) Github Action.
79
+
> - And the action'll create an issue in your fork if pulling is unsuccesfull. So you need to enable `issues` for your fork with your repositories settings (`Settings``-->``General``-->``Features``Issues`)
80
+
> - For more information on how this action works: [lobe-chat's Sync Feature Wiki - en-US](https://github.com/lobehub/lobe-chat/wiki/Upstream-Sync) & [lobe-chat's Sync Feature Wiki - zh-CN](https://github.com/lobehub/lobe-chat/wiki/Upstream-Sync.zh-CN)
81
+
82
+
> [!TIP]
83
+
> - You can change schedule by editing `- cron: '0 */6 * * *'` in [cp_pull_upstream.yml](.github/workflows/cp_pull_upstream.yml)
84
+
> - For more information on `- cron` of Github Actions, visit [Github Documentation - Scheduling Actions](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule)
85
+
86
+
> [!CAUTION]
87
+
> - IF you use another method (maybe a Github App), to sync your forks with upstream repos, (for ex: [Pull by Wei](https://github.com/wei/pull)), you should disable the `Upstream Sync` action by going through, `Actions``-->``Upstream Sync``-->``Right Top Menu [...]``-->``Disable Workflow`
88
+
> - For more information on how to disable a workflow: [Github Documentation on Disabling & Enabling Workflows](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow)
89
+
90
+
---
91
+
89
92
> [!NOTE]
90
93
> For Generic `Linux` and `MacOS` instructions, use [source repository](https://github.com/msojocs/fiddler-everywhere-enhance)
0 commit comments