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

Add works with dotenv-vault badge #29

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

motdotla
Copy link

Hey 👋 Luos team,

I continue to think it is very cool that you are using dotenv-vault in an opensource project. Here's a badge if you would like to show that off.

If there are other ways we can make dotenv-vault more useful to your open source users let us know as well. Maybe somehow automating their .env creation more easily. I'm all ears!

⚠ PLEASE DO NOT DELETE THE TEXT BELOW ⚠

Pull request's description

Added 'works with dotenv-vault' badge

Checklist before merging (please do not edit)

You must review you work before to submit the review to others.

Self-review of your content

Remember the content must be readable and understandable by someone else than yourself.

  • From a technical point of view.
  • From a grammatical point of view (spelling mistakes, typos, clarity, etc.), and following the guidelines at the bottom.

External reviews of your content

  • You requested a technical review.
  • You requested a grammatical review.
  • You validated with @K0rdan or @alexgeron-Luos that it is safe to merge.

Some guidelines to keep in mind

  • Colons (:), semi-colons (;), exclamation (!), and interrogation points (?) are not preceded by a space (like full stops and commas). E.g.: Colons!

  • File names and/or address are put in italic. E.g.: The file main.c.

  • Functions, variables, or more generally short codes are put between grave accents. E.g.: To obtain code(), type `code()`.

  • Long codes are put into blocks of code with three grave accent on each side, and the language's name:

    ```c

    // Some C language

    ```

  • "Luos engine" has a upper case on the L for "Luos" and lower case on the e for "engine".

  • We call it "Luos engine" as a proper name, and not "the Luos engine".

  • Following that fashion, anything that's owned by "Luos engine" implies that we must use 's as the standard English rule to show the possessive case, e.g. "Luos engine's API".

  • The names pipe, gate, inspector, sniffer, app or application, driver, etc. have a lower case and can be refereed with the determiner the. E.g.: The inspector.

@vercel
Copy link

vercel bot commented Jul 25, 2022

@motdotla is attempting to deploy a commit to the Luos Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants