Update CI template examples to default branch
What does this MR do?
What does this MR do?
As part of the linked issue, we should make sure all CI/CD templates all point to $CI_DEFAULT_BRANCH and not a hardcoded default branch like master.
This MR touches CI/CD template examples for various languages and tools. Since these are meant for copy/pasting into a project, and not to be used with include, I think it's safe to update these right now.
Related to #324131 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team