Add source repo url information to standard parameters

[savitaashture]

Users can now use source_repo_url in pipelinerun template to get the information from which forked repo the event (Pull Request / Push) is coming from

Ex:

spec:
  params:
    - name: source_repo_url
      value: "{{ source_repo_url }}"      
  pipelineSpec:
    params:
      - name: source_repo_url  
  ...

Signed-off-by: Savita Ashture [email protected]"

Changes

Submitter Checklist

• 📝 A good commit message is important for other reviewers to understand the context of your change. Please refer to How to Write a Git Commit Message for more details how to write beautiful commit messages. We rather have the commit message in the PR body and the commit message instead of an external website.
• ♽ Run make test before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI. (or even better install pre-commit and do pre-commit install in the root of this repo).
• ✨ We heavily rely on linters to get our code clean and consistent, please ensure that you have run make lint before submitting a PR. The markdownlint error can get usually fixed by running make fix-markdownlint (make sure it's installed first)
• 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
• 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
• 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
• 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (557ccab) 60.97% compared to head (85881f2) 60.97%.
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1385   +/-   ##
=======================================
  Coverage   60.97%   60.97%           
=======================================
  Files         136      136           
  Lines        9934     9935    +1     
=======================================
+ Hits         6057     6058    +1     
  Misses       3392     3392           
  Partials      485      485           

Files Changed	Coverage Δ
pkg/customparams/standard.go	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[chmouel]

what happen on push ? should we have the same as target_url like we had on target_branch?

and let's make sure this would be documented with a test for it (push scenario).

[savitaashture]

@chmouel

what happen on push ? should we have the same as target_url like we had on target_branch?

Yes we do same like target_branch

I mean source and target URLs are same https://github.com/openshift-pipelines/pipelines-as-code/blob/main/pkg/provider/github/parse_payload.go#L246-L247

Actually we don't get the info of source URL directly in push i searched in Github docs

Or am i missing something here 🤔

Alternative way:

I did print push payload body https://gist.github.com/savitaashture/e1013de246b201ece565a86d7da96531 we get the data in bits of pieces we need to collect those in order to provide info of source_url and source_branch for push

let's make sure this would be documented

You mean here https://pipelinesascode.com/docs/guide/authoringprs/#authoring-pipelineruns-in-tekton-directory we need to add a clarification for those standard parameters or push and pull_request
right ?

with a test for it (push scenario).

You mean e2e ?

[chmouel]

looks good, just some comments