Skip to content

Commit

Permalink
Merge pull request IntelRealSense#2845 from IntelRealSense/timor-trig…
Browse files Browse the repository at this point in the history
…ger-private-ci

Add trigger-private-ci.yaml
  • Loading branch information
timor-raiman authored Aug 14, 2023
2 parents ec7fb40 + 3b7ab9b commit b49111f
Showing 1 changed file with 45 additions and 0 deletions.
45 changes: 45 additions & 0 deletions .github/workflows/trigger-private-ci.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: Trigger Private CI
on:
workflow_dispatch:
issue_comment:
types: [created, edited]
pull_request_target:
types: [opened, reopened, synchronize]
branches: [ros2-hkr]

jobs:
doTriggerPrivateCI:
if: |
(github.event_name == 'issue_comment' && github.event.issue.pull_request && github.event.comment.body == 'rebuild!') ||
(github.event_name == 'pull_request_target') ||
(github.event_name == 'workflow_dispatch')
runs-on: ubuntu-22.04
timeout-minutes: 35
steps:
- name: Generate GitHub App Token
id: generate_token
uses: tibdex/github-app-token@v1.7.0
with:
app_id: ${{ secrets.AUTH_APP_ID }}
private_key: ${{ secrets.AUTH_APP_CLIENT_KEY }}

- name: Trigger Build in Private Repo
uses: dacbd/create-issue-action@v1.2.1
with:
token: ${{ steps.generate_token.outputs.token }}
repo: realsense-ros-private-ci
title: CheckPublicPR
body: ${{ github.event.pull_request.number }}

#ToDo:
# on the rebuild! comment, there's an issue with the sha pointing to something other than pr/merge,
# therefore, for 'rebuild!' we need to take the sha from github.event, and not github.sha

#ToDo:
# manual trigger although present, does not work, as PR number is required

#ToDo:
# support running on tips of branches rather than on Pull Request

#ToDo:
# the rebuild!! comment trigger is not limited to the ros2-development branch

0 comments on commit b49111f

Please sign in to comment.