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: CHANGELOG.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,26 +9,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
9
9
10
10
## v0.3.8 (2021-05-01)
11
11
### Fix
12
-
***model.py:**`context` now does not throw ([`82f93d9`](https://github.com/billsioros/dotify/commit/82f93d92e16860e3dd751125e0c5f72125781231))
12
+
***model.py:**`context` now does not throw ([`82f93d9`](https://github.com/the-dotify-project/dotify/commit/82f93d92e16860e3dd751125e0c5f72125781231))
13
13
14
14
### Documentation
15
-
***README.md:** Added `docs` link & badge ([`42d4abe`](https://github.com/billsioros/dotify/commit/42d4abe9b050f0cca20db6ea002e3cea07dcb6ab))
15
+
***README.md:** Added `docs` link & badge ([`42d4abe`](https://github.com/the-dotify-project/dotify/commit/42d4abe9b050f0cca20db6ea002e3cea07dcb6ab))
16
16
17
-
**[See all commits in this version](https://github.com/billsioros/dotify/compare/v0.3.5...v0.3.8)**
17
+
**[See all commits in this version](https://github.com/the-dotify-project/dotify/compare/v0.3.5...v0.3.8)**
18
18
19
19
## v0.3.5 (2021-04-27)
20
20
### Fix
21
-
***publish.yml:** Publishing via another gh-action ([`8487eb7`](https://github.com/billsioros/dotify/commit/8487eb7dc5f24ede32f5300f6f0d640fd0b21c0c))
21
+
***publish.yml:** Publishing via another gh-action ([`8487eb7`](https://github.com/the-dotify-project/dotify/commit/8487eb7dc5f24ede32f5300f6f0d640fd0b21c0c))
22
22
23
-
**[See all commits in this version](https://github.com/billsioros/dotify/compare/v0.1.5...v0.3.5)**
23
+
**[See all commits in this version](https://github.com/the-dotify-project/dotify/compare/v0.1.5...v0.3.5)**
24
24
25
25
## v0.1.5 (2021-04-17)
26
26
### Feature
27
27
28
28
- Enabled automatic releases via [GitHub Actions](.github/workflows/publish.yml)
29
29
- Enabled automatic `Changelog` generation via [GitHub Actions](.github/workflows/generate-changelog.yml)
30
30
31
-
**[See all commits in this version](https://github.com/billsioros/dotify/compare/v0.1.4...v0.1.5)**
31
+
**[See all commits in this version](https://github.com/the-dotify-project/dotify/compare/v0.1.4...v0.1.5)**
alt="GitHub commits since latest release (by SemVer)"
50
50
/>
51
51
</a>
@@ -67,7 +67,7 @@
67
67
PosixPath('SAINt JHN - 5 Thousand Singles.mp3')
68
68
```
69
69
70
-
Feel free to check the [examples](/examples) folder for more use cases!
70
+
Feel free to check the [examples](https://github.com/the-dotify-project/dotify/tree/master/examples) folder for more use cases!
71
71
72
72
## Features
73
73
@@ -82,7 +82,7 @@ Feel free to check the [examples](/examples) folder for more use cases!
82
82
83
83
## Documentation
84
84
85
-
The project's documentation can be found [here](https://billsioros.github.io/dotify/).
85
+
The project's documentation can be found [here](https://the-dotify-project.github.io/dotify/).
86
86
87
87
## Installation
88
88
@@ -92,7 +92,7 @@ pip install dotify
92
92
93
93
## Contributing
94
94
95
-
If you would like to contribute to the project, please go through the [Contributing Guidelines](https://billsioros.github.io/dotify/contributing) first.
95
+
If you would like to contribute to the project, please go through the [Contributing Guidelines](/docs/CONTRIBUTING.md) first.
Copy file name to clipboardExpand all lines: docs/CONTRIBUTING.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
@@ -8,11 +8,11 @@ This project follows the [all-contributors](https://allcontributors.org/) specif
8
8
9
9
## Code of Conduct
10
10
11
-
By participating and contributing to this project, you agree to uphold our [Code of Conduct](/CODE_OF_CONDUCT.md).
11
+
By participating and contributing to this project, you agree to uphold our [Code of Conduct](CODE_OF_CONDUCT.md).
12
12
13
13
## Getting Help
14
14
15
-
In case all you need is an answer to a question, please refrain from opening an issue and instead visit the project's [discussion page](https://github.com/billsioros/dotify/discussions/categories/q-a).
15
+
In case all you need is an answer to a question, please refrain from opening an issue and instead visit the project's [discussion page](https://github.com/the-dotify-project/dotify/discussions/categories/q-a).
16
16
17
17
## Getting Started
18
18
@@ -34,9 +34,9 @@ PRs can be a quick way to get your fix or improvement slated for the next releas
34
34
- Only fix/add the functionality in question **OR** address wide-spread whitespace/style issues, not both.
35
35
- Address a single concern in the least number of changed lines as possible.
36
36
- Be accompanied by a complete Pull Request template (loaded automatically when a PR is created).
37
-
- Add [unit or integration tests](/tests) for added or changed functionality.
37
+
- Add [unit or integration tests](https://github.com/the-dotify-project/dotify/tree/master/examples) for added or changed functionality.
38
38
- Any code related changes should be accompanied by corresponding changes to the project's documentation.
39
-
- If your pull request introduces a new feature, the corresponding `README`[section](/README.md#features) must be updated to reflect this. Make sure you also include [an example](/examples), showcasing this new functionality.
39
+
- If your pull request introduces a new feature, the corresponding `README`[section](/README.md#features) must be updated to reflect this. Make sure you also include [an example](https://github.com/the-dotify-project/dotify/tree/master/examples), showcasing this new functionality.
40
40
- Write clear, concise commit message(s) using [conventional-changelog format](https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md). [Why?](#writing-your-commit-message)
41
41
- If your PR is connected to an open issue, add a line in your PR's description that says `Fixes: #123`, where `#123` is the number of the issue you're fixing.
42
42
@@ -49,7 +49,7 @@ In general, we follow the ["fork-and-pull" Git workflow](https://github.com/susa
49
49
3. Create a branch locally with a succinct but descriptive name
50
50
4. Commit changes to the branch
51
51
5. Push changes to your fork
52
-
6.[Open a PR in our repository](https://github.com/billsioros/dotify/compare) and follow the PR template so that we can efficiently review the changes
52
+
6.[Open a PR in our repository](https://github.com/the-dotify-project/dotify/compare) and follow the PR template so that we can efficiently review the changes
53
53
54
54
## Setting up a local development environment
55
55
@@ -83,7 +83,7 @@ _**ATTENTION**: Even though, using a JSON file is far more convenient than re-ex
83
83
84
84
### Installing pre-commit hooks
85
85
86
-
The project utilizes the [pre-commit](https://pre-commit.com/) framework. Having [created a virtual environment and installed the required dependencies](#installing-poetry), you may run `pre-commit install` to install the [git hook scripts](/.pre-commit-config.yaml).
86
+
The project utilizes the [pre-commit](https://pre-commit.com/) framework. Having [created a virtual environment and installed the required dependencies](#installing-poetry), you may run `pre-commit install` to install the [git hook scripts](https://github.com/the-dotify-project/dotify/blob/master/.pre-commit-config.yaml).
87
87
88
88
### Formatting, Linting and Testing
89
89
@@ -118,7 +118,7 @@ Having made your changes, please run `mkdocs server` and make sure that no error
118
118
119
119
### Writing your commit message
120
120
121
-
The project's version number and [Changelog](/CHANGELOG.md), depend on a consistent commit history. As a result, your commit message's format is extremely important. Before opening a pull request, please make sure that your commits strictly follow the [conventional-changelog format](https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md).
121
+
The project's version number and [Changelog](https://github.com/the-dotify-project/dotify/blob/master/CHANGELOG.md), depend on a consistent commit history. As a result, your commit message's format is extremely important. Before opening a pull request, please make sure that your commits strictly follow the [conventional-changelog format](https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md).
0 commit comments