Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace ZenHub project with GitHub #2226

Merged
merged 1 commit into from
Mar 14, 2020
Merged

Replace ZenHub project with GitHub #2226

merged 1 commit into from
Mar 14, 2020

Conversation

bobcatfish
Copy link
Collaborator

Changes

We've started using GitHub for project tracking instead of ZenHub! We were using ZenHub for 2 reasons:

  1. Burndown
  2. Cross repo project planning

GitHub projects now provide (2) and we don't really use (1) anymore, so now we're using GitHub projects which have a lower barrier to usage.

@vdemeester @afrittoli @dibyom @sbwsg @wlynch

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

We've started using GitHub for project tracking instead of ZenHub! We were using ZenHub for 2 reasons:
1. Burndown
2. Cross repo project planning

GitHub projects now provide (2) and we don't really use (1) anymore, so now we're using GitHub projects which have a lower barrier to usage.
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 13, 2020
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 13, 2020
@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 13, 2020
@afrittoli
Copy link
Member

/test pull-tekton-pipeline-build-tests

@afrittoli
Copy link
Member

Linter timeout 😓

@afrittoli
Copy link
Member

Thanks! /lgtm

Copy link
Member

@vdemeester vdemeester 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 Mar 14, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom, vdemeester

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

@vdemeester
Copy link
Member

/retest

@tekton-robot tekton-robot merged commit 210d978 into master Mar 14, 2020
@vdemeester vdemeester deleted the bobcatfish-patch-2 branch March 25, 2020 06:33
@afrittoli afrittoli added the kind/documentation Categorizes issue or PR as related to documentation. label Apr 30, 2020
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. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants