Find a place for vscode settings to live without breaking GitHub OAuth
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, shell, vscode
- Domain
- authentication, developer-experience, tooling
Research direction
The issue names no files, tests, or entry points. Start by inspecting the repository for existing VS Code settings and GitHub OAuth configuration, then determine how they are currently discovered. Done means choosing and documenting a settings location that does not break GitHub OAuth.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ericboxer/dotfiles
-
Finish CSV GeneratorMay be free again @ericboxer claimed this 3037 days ago, and no pull request is open. Openenhancement
-
Clean up makeexMay be free again @ericboxer claimed this 3031 days ago, and no pull request is open. Open
-
Update CSV renaming to use CSV moduleMay be free again @ericboxer claimed this 3037 days ago, and no pull request is open. Openenhancement
All issues in ericboxer/dotfiles
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
initramfs: -type f (#18686) skips the libcurl.so.4 symlink, libcurl no longer copied into initramfsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mesonbuild/wrapdb#2961 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oSoWoSo/vOid_Community_repOsitory#330 ·
Maintainers usually reply within 1 day