From f964bcb1d90941fd59f190ec6e1f41f4567fa652 Mon Sep 17 00:00:00 2001
From: xmnlab
For my information, check the official documentation: https://packaging.python.org/en/latest/discussions/src-layout-vs-flat-layout/
In addition, you should know that to build our package we use @@ -697,10 +851,10 @@
Ready to contribute? Here’s how to set up envers
for local development.
Ready to contribute? Here’s how to set up envers
for local development.
Fork the envers
repo on GitHub.
Fork the envers
repo on GitHub.
Clone your fork locally::
@@ -743,7 +897,7 @@To run a subset of tests::
-$ pytest tests.test_envers
+$ pytest tests.test_envers
Release
This project uses semantic-release in order to cut a new release based on the
@@ -756,7 +910,7 @@
Commit message format
publishes the release.
By default, semantic-release uses
Angular Commit Message Conventions.
-The commit message format can be changed with the preset
or config
options_
+The commit message format can be changed with the preset
or config
options_
of the
@semantic-release/commit-analyzer
and
@@ -766,7 +920,7 @@
Commit message format
commitlint can be used
to help contributors and enforce valid commit messages.
The table below shows which commit message gets you which release type when
-semantic-release
runs (using the default configuration):
+semantic-release
runs (using the default configuration):
@@ -776,26 +930,26 @@ Commit message format
-fix(pencil): stop graphite breaking when pressure is applied
+fix(pencil): stop graphite breaking when pressure is applied
Fix Release
-feat(pencil): add 'graphiteWidth' option
+feat(pencil): add 'graphiteWidth' option
Feature Release
-perf(pencil): remove graphiteWidth option
+perf(pencil): remove graphiteWidth option
Chore
-BREAKING CHANGE: The graphiteWidth option has been removed
+BREAKING CHANGE: The graphiteWidth option has been removed
Breaking Release
source:
https://github.com/semantic-release/semantic-release/blob/master/README.md#commit-message-format
-As this project uses the squash and merge
strategy, ensure to apply the commit
+
As this project uses the squash and merge
strategy, ensure to apply the commit
message format to the PR's title.
diff --git a/example/index.html b/example/index.html
index db64273..a02758d 100644
--- a/example/index.html
+++ b/example/index.html
@@ -11,11 +11,11 @@
-
+
-
+
@@ -90,7 +90,7 @@