Работа с серверными лицензиями
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the licensing failure when running git init and compare how file-based and server-based licenses are discovered. The issue does not name files or tests; done means the command can locate and use an existing server license without requiring a separate file-license set.
Written by the indexing model from the issue text.
Description
При выполнении команды git init система требует файловые лицензии и не видит серверные, как-то можно указать ей где смотреть серверные? А то приходится только для этой задачи покупать новый комплект лицензий
- Dominant language
- 1C Enterprise
- Stars
- 334
- Forks
- 98
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 oscript-library/gitsync
-
УстановщикПлагинов.os:142 использует удалённый метод ПолучитьВыводКоманды() (1commands ≥ 1.5.0)Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oscript-library/gitsync#368 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
oscript-library/gitsync#355 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oscript-library/gitsync#241 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oscript-library/gitsync#366 · 2 comments ·
Maintainers usually reply within 1 day
-
Вопрос как работатьOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
oscript-library/gitsync#360 · 3 comments ·
Maintainers usually reply within 1 day
All issues in oscript-library/gitsync
Similar issues
-
area/testing kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelscope/ms-swift#10287 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day