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

Rename constants.go to storagetypes.go 💎 #1730

Merged
merged 1 commit into from
Dec 11, 2019

Conversation

bobcatfish
Copy link
Collaborator

Changes

Creating a file called constants.go encourages folks to put all const
values into this file, while I think it'll lead to better naming and
code organization in the long run to try to name files and packages
clearly after their contents. In this case I have a feeling that calling
this storagetypes might actually hint that these values belong in
another package entirely but that's a story for another day!

🙏 sorry not sorry @vdemeester 🙏

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.

Creating a file called constants.go encourages folks to put all `const`
values into this file, while I think it'll lead to better naming and
code organization in the long run to try to name files and packages
clearly after their contents. In this case I have a feeling that calling
this storagetypes might actually hint that these values belong in
another package entirely but that's a story for another day!
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Dec 10, 2019
@tekton-robot tekton-robot requested review from abayer and a user December 10, 2019 22:19
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 10, 2019
@vdemeester
Copy link
Member

/test pull-tekton-pipeline-integration-tests

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.

Creating a file called constants.go encourages folks to put all const
values into this file, while I think it'll lead to better naming and
code organization in the long run to try to name files and packages
clearly after their contents. In this case I have a feeling that calling
this storagetypes might actually hint that these values belong in
another package entirely but that's a story for another day!

I fully agree ! no need to be sorry 😉 🤗

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 11, 2019
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2019
@tekton-robot tekton-robot merged commit 1f93a30 into tektoncd:master Dec 11, 2019
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 lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants