Skip to main content

M1-2022-git

Introduction

This repository is a fork from the previous repository. The bugs in the converter have been fixed and now we want to publish our work as a publicly available python package.

Getting started

You should be working from your own repository that is a fork of M1-2022-git-workflow. In order to run this project, you will have to follow these steps.

  1. Clone this project
  2. move into the project folder
cd M1-2022-git-workflow
  1. Set up a virtual environment
  • Create the virtual environment
python -m venv myvenv
  • Activate venv
. venv/bin/activate
  1. Install pytest
pip install -U pytest
  1. Execute main script
python main.py

Instructions

Merge feature branch into dev

Now that the converter has no more bugs, we want to merge our branch feature into the dev branch. We will do a pull request (on your own repo). On GitHub, go to the "Pull requests tab" and click "New pull request". Select base and compare. Remember : we want to merge decimal-binary-converter into dev. Then, Create the pull request. Add some description of the work you have done and publish the Pull Request.

Note : We could have just merge decimal-binary-converter into dev from the command line. However, when working on a real project, you probably won't have the rights to do so. Remember : dev is a public branch. So all the work going down there should be carefully reviewed and tested.

Publish your work

We now have an awesome binary/decimal two ways converter ! It's time to publish it so the rest of the world can enjoy it ! We will publish it on PyPI (Python Package Index) which is a public repository of softwares for Python.

  1. First, you have to create an account on Pypi.org
  2. Then, in your repository, you will find a .github directory
  3. Inside this directory, you will find .yml files that defines workflows (using GitHub actions)
  4. Open the yml files and take time to understand them. Do not hesitate to ask the teacher about them

Hands on !

  1. We want to create a workflow that will, on publish, test our code and if tests succeed, then publish our package on PyPI
  2. In GitHub, click on the Actions tab, then click on new workflow
  3. Choose among the suggestions the template that best suits your use-case and click Configure
  4. You may find some useful informations in the Python documentation
  5. When creating a release on GitHub, do not forget to create a tag corresponding to that release

Pull request

  1. Once the workflow is setup and tested (you have published your package using it) you can open a pull request to the original repository

Metadata

Release files for Aygan3 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Aygan3 0.0.1
File Size Uploaded Provenance
aygan3-0.0.1.tar.gz 8.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for Aygan3 0.0.1
File Interpreter ABI Platform
aygan3-0.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 15.0 kB

Release files / aygan3-0.0.1.tar.gz

Download URL aygan3-0.0.1.tar.gz
Size 8.2 kB
Tags Source
SHA-256 checksum
How to use checksums
f31dbaf013cd6fcfa76b19e4f95848b49f3290e6dc5d868c095f8c3c427b887e
BLAKE2b-256 checksum
How to use checksums
03b2f6b8df7425a8b2abc766922e5097c09b42562d7d54e5d2d604df153803ca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.14

Release files / aygan3-0.0.1-py3-none-any.whl

Download URL aygan3-0.0.1-py3-none-any.whl
Size 6.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ee1fa73826ffaf7f9890a497e5ac90dee67bbc43d848860a1ed821c251028eb9
BLAKE2b-256 checksum
How to use checksums
cd58e13ea12ed1a3a049a94465bc09ee50bd63db96fd5e206b757947cbf9b432
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.14

Security for Aygan3 0.0.1

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.

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page