You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/blog/first-time-contributors/index.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,10 +161,10 @@ It's worth noting that some organizations, such as the Open Source Initiative (O
161
161
$ git config --global pull.rebase true
162
162
```
163
163
164
-
OSL recommend the usage of git rebase
164
+
OSL recommends the usage of git rebase
165
165
166
166
167
-
## Mergin a Pull Requests (PRs)
167
+
## Merging a Pull Request (PR)
168
168
Pull requests (PRs) are essential for collaborative software development, enabling contributors to propose changes to a project's codebase. Once a PR is submitted, it undergoes a review process before being merged into the main codebase. Here are three common methods for merging PRs:
169
169
170
170
#### 1. Merge Commit:
@@ -285,7 +285,7 @@ GitFlow, developed by Vincent Driessen, provides a more organized approach to br
285
285
286
286
Choosing between GitHub Flow and GitFlow depends on your team's specific needs and project requirements:
287
287
288
-
- **GitHub Flow**: Ideal for teams focused on continuous delivery, rapid iteration, and simplicity. This is most used in a bunch of proyects.
288
+
- **GitHub Flow**: Ideal for teams focused on continuous delivery, rapid iteration, and simplicity. This is most used in a bunch of projects.
289
289
- **GitFlow**: Suited for larger projects with longer release cycles, strict versioning, and a more structured approach to development.
290
290
291
291
While both workflows have their merits, it's essential to assess your team's workflow preferences, project size, and release cycle frequency before making a decision.
@@ -294,7 +294,7 @@ While both workflows have their merits, it's essential to assess your team's wor
294
294
295
295
For a deeper dive into GitFlow's advantages and implementation details, consider referring to the following blog post: [click here](https://lucamezzalira.medium.com/git-flow-vs-github-flow-76b93f4782f7).
296
296
297
-
OSL recommend the github flow
297
+
OSL recommends the github flow
298
298
299
299
## Python Linters Overview
300
300
@@ -389,15 +389,15 @@ When starting a new Python project, it's beneficial to use project templates tha
389
389
390
390
- **Cookiecutter**: Cookiecutter is a command-line utility that generates projects from project templates. It prompts you for project-specific details and then creates a customized project structure based on the selected template. There are many community-contributed templates available for various types of Python projects, including web applications, libraries, and data analysis projects.
391
391
392
-
- **SciCookie**: SciCookie is a project template ocused on the scientific python community, but it can be used by any python project. It includes a structured directory layout, documentation templates, and example code snippets. SciCookie helps streamline the setup process for scientific Python projects and encourages best practices in testing and documentation.
392
+
- **SciCookie**: SciCookie is a project template focused on the scientific python community, but it can be used by any python project. It includes a structured directory layout, documentation templates, and example code snippets. SciCookie helps streamline the setup process for scientific Python projects and encourages best practices in testing and documentation.
393
393
394
394
In summary, while `unittest` provides a robust framework for writing unit tests in Python, alternative frameworks like Pytest and Hypothesis offer additional features and flexibility. When starting a new project, leveraging project templates such as `scicookie` with tools like `cookiecutter` can accelerate setup and promote best practices in project organization and testing.
395
395
396
-
# What is a virtual enviroments and why it is important?
396
+
# What is a virtual enviroment and why is it important?
397
397
398
398
A virtual environment is a self-contained directory that isolates the dependencies for a specific project, regardless of the programming language. It can house an interpreter (like Python) along with its associated libraries, but it can also manage dependencies for other languages and tools. This isolation ensures that the project's requirements don't conflict with those of other projects on the same system.
399
399
400
-
When you create a virtual environment for each of your project, it essentially creates a sandboxed environment where you can install packages and dependencies without affecting the global Python installation on your system. This isolation is crucial because different projects often require different versions of libraries or dependencies, and conflicts can arise if they share the same environment.
400
+
When you create a virtual environment for each of your projects, it essentially creates a sandboxed environment where you can install packages and dependencies without affecting the global Python installation on your system. This isolation is crucial because different projects often require different versions of libraries or dependencies, and conflicts can arise if they share the same environment.
401
401
402
402
Creating virtual environments is crucial for several reasons:
0 commit comments