Skip to content

Conversation

@heyvister1
Copy link
Collaborator

@heyvister1 heyvister1 commented Nov 14, 2024

Fixing docs-ci workflow to be triggered upon the following use cases:

  1. pull-request (new/modified)
  2. tag
  3. branch

Examples for propagated workflow env variables:

TAG: v1.0-tag-workflow
REF_NAME: v1.0-tag-workflow
REF_HEAD: 
PR_NUMBER: 
PR_TITLE_PREFIX: task: update documentation for
COMMIT_SUFFIX: v1.0-tag-workflow
DOWNSTREAM_REPO_OWNER: nvidia-ci-cd
DOWNSTREAM_FEATURE_BRANCH: update-docs-for-v1.0-tag-workflow
UPSTREAM_REPO_OWNER: Mellanox
UPSTREAM_DEFAULT_BRANCH: main
---
REF_NAME: 5/merge
REF_HEAD: test-pr-workflow
PR_NUMBER: 5
PR_TITLE_PREFIX: task: update documentation for
COMMIT_SUFFIX: pull/5
DOWNSTREAM_REPO_OWNER: nvidia-ci-cd
DOWNSTREAM_FEATURE_BRANCH: update-docs-for-test-pr-workflow
UPSTREAM_REPO_OWNER: Mellanox
UPSTREAM_DEFAULT_BRANCH: main

1. pull-request (new/modified)
2. tag
3. branch

Signed-off-by: Ido Heyvi <iheyvi@nvidia.com>
@rollandf rollandf merged commit 2762b2e into Mellanox:main Nov 14, 2024
1 check passed
e0ne added a commit to Mellanox/network-operator that referenced this pull request Nov 15, 2024
…nges (#1162)

Following `docs-ci-trigger` changes will initiate new
`network-operator-docs` repo PR for new `tag`, `pull-request` cases,
whenever there are helm values or api changes.

This PR is based on changes done in
[#Mellanox/network-operator-docs/132](Mellanox/network-operator-docs#132)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants