Skip to content

Purge .env from commit history #2

@jonathanfoster

Description

@jonathanfoster

Even though the .env file doesn't contain any sensitive info, it's best practice to not commit it to version control. There's already instructions in the README to create a new one so there shouldn't be any usability issues. It would also be nice not to have the wife's phone number in Github for spammers to find (more her problem than mine really).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions