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
Copy file name to clipboardExpand all lines: README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ GitHub Action for automatically syncing LeetCode submissions to a GitHub reposit
55
55
leetcode-session: ${{ secrets.LEETCODE_SESSION }}
56
56
destination-folder: my-folder
57
57
verbose: true
58
-
commit-header: '[LeetCode Sync]'
58
+
commit-header: "[LeetCode Sync]"
59
59
```
60
60
61
61
6. After you've submitted a LeetCode solution, run the workflow by going to the `Actions` tab, clicking the action name, e.g. `Sync Leetcode`, and then clicking `Run workflow`. The workflow will also automatically run once a week by default (can be configured via the `cron` parameter).
@@ -101,6 +101,7 @@ Since this file is in the `.gitignore` file to avoid users accidentally committi
101
101
This likely means that you hit a rate limit when committing to GitHub (this may happen if you have over ~300 submissions initially). Since the syncer writes in reverse chronological order, it should pick up syncing submissions from where it left off on the next run of the workflow, so just retry the workflow manually after some time.
102
102
103
103
#### Job fails with "HttpError: Resource not accessible by integration"
104
+
104
105
This means the github token you're using does not have permission to write to your repo. If you're using the default `github.token` method follow the instructions [here] (https://docs.github.com/en/actions/security-guides/automatic-token-authentication)
0 commit comments