yt-transcript-dl
TODO
Initial setup
Before we can start we need to do some initial configuration. First we need to install all the dependencies. You can do this by executing the following command:
make install
You might have noticed that an initial commit was performed. This initial commit contains the starting point of the cookiecutter template plus the generated pyproject.toml.
Now it's time to configure your remote GitHub repository:
git remote add origin <REMOTE ADDRESS>
Configuring the main branch
Push the current main branch to the remote, using the following commands:
git branch -M main
git push -u origin main
Configuring the develop branch
Next, we will create a develop branch. You can use the following commands:
git checkout -b develop
git push --set-upstream origin develop
Tip: You can now set the default branch to
develop!
Configure PyPi
To automatically upload release to PyPi type the following command:
make release
You will be prompted for your username and password. After you created the initial release you can navigate to your projects. For your package, navigate to Manage, Settings and Create a token for k8s-image-registry-secret.
Pick an username and set the scope to the package you just created. Use the generated token to create a secret in GitHub.
On GitHub in your repository, go to Settings, Security, Secrets and then Actions. Here you will be able to create the repository secret.
Use PYPI_API_TOKEN as the name and the token from the previous step as the secret value.
[Optional] Codecov.io
You can add the following to your .github/workflows/ci.yml file to enable Codecov.io
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v2
with:
fail_ci_if_error: true
token: ${{ secrets.CODECOV_TOKEN }}
files: ./reports/coverage.xml
- name: Code Coverage Summary Report
uses: irongut/CodeCoverageSummary@v1.1.0
with:
filename: reports/coverage.xml
badge: true
fail_below_min: true
format: markdown
output: both
thresholds: 95 100
Configure Codecov.io
Login to codecov.io locate your repository. Navigate to the Settings and then General. There you will find the CODECOV_TOKEN that you need to add to your GitHub repository.
Go to Settings, Security, Secrets and then Actions. Here you will be able to create the repository secret.
Configure coverage report
You will need to add the following to test target in the Makefile:
.PHONY: test
test: complexity-baseline ## Run the tests defined in the project
pytest --junitxml=reports/pytest.xml --cov-report xml:reports/coverage.xml
Metadata
Release files for yt-transcript-dl 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| yt_transcript_dl-0.1.0.tar.gz | 3.7 kB | Without provenance | Details for yt_transcript_dl-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| yt_transcript_dl-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for yt_transcript_dl-0.1.0-py3-none-any.whl |
Total release size: 8.2 kB
Release files / yt_transcript_dl-0.1.0.tar.gz
| Download URL | yt_transcript_dl-0.1.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bf6760ec721f64342be5772bbdd65f5c7bc1186453d3b462dcd5c5d4173a6f6
|
|
BLAKE2b-256 checksum How to use checksums |
d422e78d28c802436070799b458cc28e278fa9e4188bb5f6b14b9d716211e3b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.3 Linux/6.4.12-arch1-1
|
Release files / yt_transcript_dl-0.1.0-py3-none-any.whl
| Download URL | yt_transcript_dl-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a5d12a0eaa4317da8683afcf9697aeff78e7415bac38a5465c79e8179ca580b
|
|
BLAKE2b-256 checksum How to use checksums |
920b82df1867e08715fc814a85c9bc4181803b03b935a66635f29a92fa0041bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.3 Linux/6.4.12-arch1-1
|
Security for yt-transcript-dl 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.