Skip to content

Conversation

@vdemeester
Copy link
Member

Changes

The problem was that the workflow was trying to use
context.issue.number and github.event.issue.number, which aren't
available in repository_dispatch events.

Signed-off-by: Vincent Demeester [email protected]

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

The problem was that the workflow was trying to use
context.issue.number and github.event.issue.number, which aren't
available in repository_dispatch events.

Signed-off-by: Vincent Demeester <[email protected]>
@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. release-note-none Denotes a PR that doesnt merit a release note. labels Nov 28, 2025
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 28, 2025
@vdemeester
Copy link
Member Author

/cc @AlanGreene @afrittoli @waveywaves

@tekton-robot
Copy link
Collaborator

@vdemeester: GitHub didn't allow me to request PR reviews from the following users: AlanGreene.

Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @AlanGreene @afrittoli @waveywaves

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Contributor

@khrm khrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2025
owner: context.repo.owner,
repo: context.repo.repo,
pull_number: context.issue.number
pull_number: ${{ github.event.client_payload.github.payload.issue.number }}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I could use context.payload.client_payload.github.payload.issue.number as well

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

both fine

Copy link
Member

@twoGiants twoGiants left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@afrittoli
Copy link
Member

/e2e-extras

@tekton-robot
Copy link
Collaborator

Something went wrong with your /e2e-extras command: [please check the logs][1].

[1]:

@afrittoli
Copy link
Member

Uhm, when routing commands, it doesn't pick up the version of the workflow from the PR, which makes it a problem for testing the slash commands themselves. We'll test it once it's merged.

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, twoGiants

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 28, 2025
@vdemeester
Copy link
Member Author

Uhm, when routing commands, it doesn't pick up the version of the workflow from the PR, which makes it a problem for testing the slash commands themselves. We'll test it once it's merged.

Yeah.. it's a bit a shot in the dark. If it fails again, I'll replicate this on my workflow-experiments repo to figure out what happens.

@afrittoli
Copy link
Member

/retest

@tekton-robot tekton-robot merged commit ad5317e into tektoncd:main Dec 1, 2025
155 of 165 checks passed
@github-project-automation github-project-automation bot moved this from Todo to Done in Tekton Community Roadmap Dec 1, 2025
@vdemeester vdemeester deleted the fix-e2e-extra-workflow branch December 1, 2025 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants