Add integration tests for cloning GitLab repositories
Open
Nobody has claimed this yet.
git_service
tests
- Dominant language
- Python
- Stars
- 210
- Forks
- 36
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
We need some integration tests for cloning GitLab repositories. The following cases should be covered:
- Cloning a public repository from the public GitLab service, without an access token.
- Cloning a private repository from the public GitLab service, with an access token.
- Cloning a repository from a private GitLab service, with an access token.
Managing the access token in the GitHub Actions environment is one potential technical problem to consider.
Related issues: #316.
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 existing repository-cloning integration-test entry points and the GitHub Actions environment configuration. Run the current integration tests, then cover public and private repositories on the public GitLab service and a private GitLab service, including access-token handling. Done means all three cases run successfully in the intended test environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100