openedx / openedx/openedx-atlas
feat: Support non-GitHub repositories
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 13
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
This one goes without saying. Some maintainers would need to pull from Gitlab or their own git repo.
Atlas should allow any git repository to be used:
-
--repository=openedx/openedx-translations: A single/found, therefore assumes GitHub repo slug and cloneshttps://github.com/openedx/openedx-translations.git -
--repository=https://github.com/test/our-translations.git:https://is found therefore assumes full URL and checks outhttps://github.com/test/our-translations.git -
--repository=git@gitlab.com:another/translations.git:@is found, therefore assumes full URL and checks outgit@gitlab.com:another/translations.git
Contributor 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.
Research direction
Start by locating the CLI handling for the --repository option and the code that clones or checks out the translation repository. Compare the current GitHub-slug behavior with the three repository forms in the issue; done means GitHub slugs, HTTPS URLs, and SSH-style Git URLs are each accepted and used for checkout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100