git-resource
git-resource copied to clipboard
tracks commits in a branch of a Git repository
In a pipeline with: ``` - put: git-repo params: repository: git-repo tag: git-tag/tag.txt tag_only: true ``` [You use the following command](https://github.com/concourse/git-resource/blob/f0d57ba2b7d43eb37dd001e14fe8bbb874b9a49a/assets/out#L105-L107): ``` push_tags() { git push --tags push-target $forceflag }...
I have (had) a gitea instance with SSH open at port 22001 which makes the SSH clone URI `ssh://[email protected]:22001/user/repo.git` instead of the normal `[email protected]:user/repo.git` which only works with port 22....
Hi, I have two different git resources pointing to the same repository; one of them has a paths option pointing to a specific subdirectory. I'm finding that even changes outside...
I recently did a static code scan of the final Concourse BOSH release for 7.7.0 and came across several findings related to the resource types which are packed as root...
I'm trying to access a GitLab instance using an ed25519 keypair. The resource config is as follows: ``` resources: - name: source-code type: git source: uri: git@my-gitlab-server:test/test.git branch: master private_key:...
If a nested submodule is configured to be "shallow", referencing a commit that is not reachable from the respective repository's HEAD (typically the default branch, if e.g. hosted on GitHub),...
I have an environment where, to access git repos, I need to specify two http.extraHeader values. If I provide them to a git resource as ``` git_config: - name: http.extraHeader...
Hi, We have quite a few submodules in one of our projects and at the moment it can take about 10 minutes just to clone the repo + submodules. Concourse...
At least since the release on April 3rd the git-resource has stopped working as expected. the Additional files populated section seem to not get populated with anything and this has...
This resource tracks some [useful metadata](https://github.com/concourse/git-resource/blob/master/assets/common.sh#L177-L185) that is not written to files by the `in` command, which makes it impossible to reference that metadata during pipeline execution. I think it...