Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

TEP-0115: Add git revision resolution support in Git Resolver #75

Conversation

QuanZhang-William
Copy link
Member

@QuanZhang-William QuanZhang-William commented Jul 27, 2022

Add git revision resolution support in Git Resolver

Prior to this change, users need to specify git commit or branch fields when using git resolver. This commits replaces the commit and branch with revision fields, which support git commit, branch and tag. This change extends the usability of git resolver and also provides a better user experience.

@tekton-robot
Copy link

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@tekton-robot tekton-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 27, 2022
@tekton-robot tekton-robot requested review from abayer and a user July 27, 2022 20:26
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 27, 2022
@QuanZhang-William
Copy link
Member Author

/test all

@abayer
Copy link
Contributor

abayer commented Jul 28, 2022

Looks good!

@QuanZhang-William QuanZhang-William force-pushed the tep-0110-add-git-revision-resolution-support branch from 581adcd to 455d3c7 Compare July 29, 2022 15:56
@QuanZhang-William QuanZhang-William marked this pull request as ready for review July 29, 2022 15:58
@tekton-robot tekton-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 29, 2022
@QuanZhang-William
Copy link
Member Author

/assign @jerop

QuanZhang-William added a commit to QuanZhang-William/pipeline that referenced this pull request Jul 29, 2022
Part of TEP-0110

Update Git Resolver example to use ```revision``` and ```pathInRepo``` fields to reflect the changes in [TEP-0110: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
QuanZhang-William added a commit to QuanZhang-William/pipeline that referenced this pull request Jul 29, 2022
Part of TEP-0115

Update Git Resolver example to use ```revision``` and ```pathInRepo``` fields to reflect the changes in [TEP-0110: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
QuanZhang-William added a commit to QuanZhang-William/pipeline that referenced this pull request Jul 29, 2022
Part of TEP-0115

Update Git Resolver example to use ```revision``` and ```pathInRepo``` fields to reflect the changes in [TEP-0115: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
@QuanZhang-William QuanZhang-William changed the title TEP-0110: Add git revision resolution suppot in Git Resolver TEP-0115: Add git revision resolution suppot in Git Resolver Jul 29, 2022
Prior to this change, users need to specify git commit or branch fields when using git resolver. This commits replaces the "commit" and "branch" with "revision" fields, which support git commit, branch and tag. This change extends the usability of git resolver and also provides a better user experience.
@QuanZhang-William QuanZhang-William force-pushed the tep-0110-add-git-revision-resolution-support branch from 455d3c7 to b1395cd Compare July 29, 2022 17:43
@abayer
Copy link
Contributor

abayer commented Aug 2, 2022

/approve

I'll give it a couple days to see if anyone else has thoughts on this, and then I'll lgtm it, and incorporate this change into my work-in-progress on moving Resolution into Pipeline.

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 2, 2022
Copy link
Member

@jerop jerop left a comment

Choose a reason for hiding this comment

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

TEP-0115 has not yet been merged but this change is useful in remote resolution either way

Thank you @QuanZhang-William!

@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer, jerop

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

The pull request process is described here

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

@jerop
Copy link
Member

jerop commented Aug 8, 2022

/lgtm

switching my approval to lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 8, 2022
@tekton-robot tekton-robot merged commit 36a5cbd into tektoncd:main Aug 8, 2022
QuanZhang-William added a commit to QuanZhang-William/pipeline that referenced this pull request Aug 8, 2022
Part of TEP-0115

Update Git Resolver example to use ```revision``` and ```pathInRepo``` fields to reflect the changes in [TEP-0115: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
@QuanZhang-William QuanZhang-William changed the title TEP-0115: Add git revision resolution suppot in Git Resolver TEP-0115: Add git revision resolution support in Git Resolver Aug 8, 2022
QuanZhang-William added a commit to QuanZhang-William/resolution that referenced this pull request Aug 8, 2022
Part of TEP-0115
Update Git Resolver documentation to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution support in Git Resolver](tektoncd#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd#51)
QuanZhang-William added a commit to QuanZhang-William/resolution that referenced this pull request Aug 8, 2022
Part of TEP-0115
Update Git Resolver documentation to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution support in Git Resolver](tektoncd#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd#51)
QuanZhang-William added a commit to QuanZhang-William/resolution that referenced this pull request Aug 8, 2022
Part of TEP-0115
Update Git Resolver documentation to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution support in Git Resolver](tektoncd#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd#51)
QuanZhang-William added a commit to QuanZhang-William/pipeline that referenced this pull request Aug 8, 2022
Part of TEP-0115

Update git resolver example to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
tekton-robot pushed a commit that referenced this pull request Aug 8, 2022
Part of TEP-0115
Update Git Resolver documentation to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution support in Git Resolver](#75) and [Add core Reconciler testing and fake resolver framework functions](#51)
tekton-robot pushed a commit to tektoncd/pipeline that referenced this pull request Aug 9, 2022
Part of TEP-0115

Update git resolver example to use "revision" and "pathInRepo" fields to reflect the changes in [TEP-0115: Add git revision resolution suppot in Git Resolver](tektoncd/resolution#75) and [Add core Reconciler testing and fake resolver framework functions](tektoncd/resolution#51)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants