Add direnv support with boilerplate

[vdemeester]

Changes

This add a .envrc file that will be used by direnv to setup the environment for the project if direnv is enabled. It also adds a .env.sample to give an example of what it could be useful for. And it adds .env to gitignore to make sure people do not commit their specific environment configurations.

/cc @tektoncd/cli-maintainers

Submitter Checklist

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

• Includes tests (if functionality changed/added)
• Run the code checkers with make check
• Regenerate the manpages, docs and go formatting with make generated
• Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from vdemeester after the PR has been reviewed.

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chmouel]

I already have a .envrc for some of my specific things on cli, and why this needs to be in repo ?

[vdemeester]

I already have a .envrc for some of my specific things on cli, and why this needs to be in repo ?

Could it move in the .env file ? The main idea is to, possibly, share some .envrc setup where it make sense, and allow users, through the .env file, to set their own.

[chmouel]

what kind of shared task do you have in mind?

isn't pre-commit something more appropriate if it's lint/checks/code related?

[vdemeester]

what kind of shared task do you have in mind?

isn't pre-commit something more appropriate if it's lint/checks/code related?

pre-commit is, imo, a tad different (and orthogonal to this), although .envrc could be use to make sure pre-commit is setup if available (so this would be one "shared" task of the .envrc). The .envrc is definitely not for any checks, it's to "help" setup the development environment the best (if enabled) and automatically.

[vdemeester]

@chmouel for example, #2176

[chmouel]

We discussed this a bit offline and it's probably a bad idea for security (since it bypass the direnv allow model) and make it a bit awkward for folks that already have their own .envrc