gitignore VS public-apis

In conclusion, the Gitignore repository stands as a testament to the power of collective knowledge and collaboration in software development. By providing a centralized repository of .gitignore templates, it empowers developers to streamline their workflow, maintain cleaner repositories, and focus on what they do best – writing exceptional code. As the software development landscape continues to evolve, the significance of .gitignore templates as indispensable tools for developers is set to endure.

The challenge here was actually from my #48in28 Exercism participation, where I am pretty familiar the standard layout for some repositories since I am familiar with tooling and language, working with new languages does not come with the same familiarity, so I found it made sense to use canonical definitions, hence the use of github/gitignore.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

Here you can find ready-made .gitignore templates for various technologies and languages such as Python, Java, Kotlin, Go, and many others: https://github.com/github/gitignore/tree/main.

You could also use this git ignore template. Create you .gitignore and add the contents from that file in.

I've only used free Unity with GitHub or GitLab, professionally and reaching back into internships. One recommendation would be to use a slightly longer .gitignore than the default, like this one.

Virtual Environments are a feature that has been part of python itself since version 3.3. It allows you to isolate both a python version and any packages you install with it. Every python project I develop with uses a virtual environment for such isolation purposes. Now I generally like to create these virtual environments inside the target project's directory so I know exactly what it's tied to. If you use GitHub's python gitignore file naming the virtual environment folder as venv or .venv will ensure it doesn't get committed (which you don't want). So I'll make a new project folder and create a virtual environment inside of it:

Especially considering the GitHub .gitignore template for Node only ignores .env.local, not .local.env: https://github.com/github/gitignore/blob/main/Node.gitignore...

# Get latest from https://github.com/github/gitignore/blob/main/Unity.gitignore

For inspirations on what type of agents I should build, I turned to the Public APIs GitHub repository which has a curated lists of free APIs. I narrowed my search for an API that does not require sign-up or an API key and returns useful information. I ultimately decided to use the Free Currency Exchange Rates API, which seemed promising upon some basic testing.

✅ public-apis/public-apis : https://github.com/public-apis/public-apis

Public-Apis Github Repo — A list of free public APIs.

Interesting thread at https://github.com/public-apis/public-apis/issues/3104

Use curl to access a free public API and get a random joke, cat fact, or whatever.

I remember the forking of https://github.com/public-apis/public-apis and the long git issue discussions. The company owning the repository stopped maintaining it but didn't give up control either. Over the years you've put in a lot of work in publicapis.dev and that is much appreciated.

Also, that isn't really a list of "contributors", but of "organisations with the most stars". Those are different things.

For example "public-apis"[1] didn't "contribute" anything as that's not a person, and looking at GitHub[2] there are a bunch of substantial contributors (the person who created the organisation/repo only has 12 commits by the way);

[1]: https://opensource-heroes.com/o/public-apis

[2]: https://github.com/public-apis/public-apis/graphs/contributo...