tektoncd / tektoncd/pipelines-as-code
test: Add e2e test for pull_request_number on push event after PR merge
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
Currently, there are no end-to-end (e2e) tests to verify that the pull_request_number dynamic variable is correctly populated when a push event is triggered by a pull request merge. This leaves a gap in our test coverage and could lead to undetected regressions.
This issue, inspired by the discussion in #2118, is to add an e2e test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading discussion #2118 and locating the repository's existing e2e tests for push events and dynamic variables. Add coverage for a push event caused by a pull request merge, verifying that pull_request_number is populated; the test passes when this value is correctly observed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100