docs: update GitLab links (21e3659e) · Commits · to be continuous... / Go

.gitlab/merge_request_templates/new_feature.md

+2 −2

Original line number	Diff line number	Diff line
		@@ -8,8 +8,8 @@ Closes #999
		## Checklist

		* General:
		* [ ] use [rules](https://docs.gitlab.com/ee/ci/yaml/#rules) instead of [only/except](https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-advanced)
		* [ ] optimized [cache](https://docs.gitlab.com/ee/ci/caching/) configuration (wherever applicable)
		* [ ] use [rules](https://docs.gitlab.com/ci/yaml/#rules) instead of [only/except](https://docs.gitlab.com/ci/yaml/#onlyexcept-advanced)
		* [ ] optimized [cache](https://docs.gitlab.com/ci/caching/) configuration (wherever applicable)
		* Publicly usable:
		* [ ] untagged runners
		* [ ] no proxy configuration but support `http_proxy`/`https_proxy`/`no_proxy`

CONTRIBUTING.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -61,7 +61,7 @@ To contribute:

		1. Create an issue describing the bug or enhancement you want to propose (select the right issue template).
		2. Make sure the issue has been reviewed and agreed.
		3. Create a Merge Request, from your own fork (see [forking workflow](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) documentation).
		3. Create a Merge Request, from your own fork (see [forking workflow](https://docs.gitlab.com/user/project/repository/forking_workflow/) documentation).
		Don't hesitate to mark your MR as `Draft` as long as you think it's not ready to be reviewed.

		### Git Commit Conventions

README.md

+7 −7

Original line number	Diff line number	Diff line
		@@ -4,8 +4,8 @@ This project implements a GitLab CI/CD template to build, test and analyse your

		## Usage

		This template can be used both as a [CI/CD component](https://docs.gitlab.com/ee/ci/components/#use-a-component)
		or using the legacy [`include:project`](https://docs.gitlab.com/ee/ci/yaml/index.html#includeproject) syntax.
		This template can be used both as a [CI/CD component](https://docs.gitlab.com/ci/components/#use-a-component)
		or using the legacy [`include:project`](https://docs.gitlab.com/ci/yaml/#includeproject) syntax.

		### Use as a CI/CD component

		@@ -112,7 +112,7 @@ If `GO_TEST_IMAGE` is set, separate `go-build` and `go-test` jobs will be run in

		Separating `build` and `test` jobs can be useful to use different images (and hence different tools) or if you want to build muli-platform binaries.

		Here is a `.gitlab-ci.yml` example that triggers a build on 3 target platforms using the [parallel matrix jobs](https://docs.gitlab.com/ee/ci/yaml/#parallel-matrix-jobs) pattern:
		Here is a `.gitlab-ci.yml` example that triggers a build on 3 target platforms using the [parallel matrix jobs](https://docs.gitlab.com/ci/yaml/#parallel-matrix-jobs) pattern:

		```yaml
		variables:
		@@ -151,9 +151,9 @@ In addition to a textual report in the console, the test jobs produce the follow
		\|-----------------------------------------------------\|------------------------------------------------------------------------------------\|-----------------------------------------------------------------------------------------------------------------------\|
		\| `$GO_PROJECT_DIR/reports/go-test.native.txt` \| native Go test report (text) \| N/A \|
		\| `$GO_PROJECT_DIR/reports/go-test.native.json` \| native Go test report (json) \| [SonarQube integration](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/test-coverage/test-execution-parameters/#go) \|
		\| `$GO_PROJECT_DIR/reports/go-test.xunit.xml` \| [xUnit](https://en.wikipedia.org/wiki/XUnit) test report(s) \| [GitLab integration](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsjunit) \|
		\| `$GO_PROJECT_DIR/reports/go-test.xunit.xml` \| [xUnit](https://en.wikipedia.org/wiki/XUnit) test report(s) \| [GitLab integration](https://docs.gitlab.com/ci/yaml/artifacts_reports/#artifactsreportsjunit) \|
		\| `$GO_PROJECT_DIR/reports/go-coverage.native.out` \| native Go coverage \| N/A \|
		\| `$GO_PROJECT_DIR/reports/go-coverage.cobertura.xml` \| [Cobertura XML](https://gcovr.com/en/stable/output/cobertura.html) coverage report \| [GitLab integration](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscoverage_report) \|
		\| `$GO_PROJECT_DIR/reports/go-coverage.cobertura.xml` \| [Cobertura XML](https://gcovr.com/en/stable/output/cobertura.html) coverage report \| [GitLab integration](https://docs.gitlab.com/ci/yaml/artifacts_reports/#artifactsreportscoverage_report) \|

		### `go-ci-lint` job

		@@ -171,7 +171,7 @@ In addition to a textual report in the console, this job produces the following

		\| Report \| Format \| Usage \|
		\|-------------------------------------------------------\|----------------------------------------------------------\|-------------------------------------------------------------------------------------------------------------\|
		\| `$GO_PROJECT_DIR/reports/go-ci-lint.codeclimate.json` \| [Code Climate](https://docs.codeclimate.com/docs/pylint) \| [GitLab integration](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscodequality) \|
		\| `$GO_PROJECT_DIR/reports/go-ci-lint.codeclimate.json` \| [Code Climate](https://docs.codeclimate.com/docs/pylint) \| [GitLab integration](https://docs.gitlab.com/ci/yaml/artifacts_reports/#artifactsreportscodequality) \|
		\| `$GO_PROJECT_DIR/reports/go-ci-lint.checkstyle.xml` \| Checkstyle \| [SonarQube integration](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/importing-external-issues/external-analyzer-reports/) \|

		### `go-semgrep` job
		@@ -199,7 +199,7 @@ In addition to a textual report in the console, this job produces the following

		\| Report \| Format \| Usage \|
		\| ------ \| ------ \| ----- \|
		\| `$GO_PROJECT_DIR/reports/golang-semgrep.gitlab.json` \| [GitLab's SAST format](https://semgrep.dev/docs/cli-reference#semgrep-scan-command-options) \| [GitLab integration](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportssast) \|
		\| `$GO_PROJECT_DIR/reports/golang-semgrep.gitlab.json` \| [GitLab's SAST format](https://semgrep.dev/docs/cli-reference#semgrep-scan-command-options) \| [GitLab integration](https://docs.gitlab.com/ci/yaml/artifacts_reports/#artifactsreportssast) \|
		\| `$GO_PROJECT_DIR/reports/golang-semgrep.native.json` \| [Semgrep's JSON format](https://semgrep.dev/docs/cli-reference#semgrep-scan-command-options) \| [DefectDojo integration](https://docs.defectdojo.com/en/connecting_your_tools/parsers/file/semgrep/)<br/>_This report is generated only if DefectDojo template is detected_ \|

		### `go-mod-outdated` job