| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | chore: release v3.11.0v3.11.0 | github-actions | 2022-10-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.10.0v3.10.0 | github-actions | 2022-09-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.9.0v3.9.0 | github-actions | 2022-08-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.8.1v3.8.1 | github-actions | 2022-08-10 | 1 | -1/+1 |
| | | |||||
| * | chore: consolidate license and authors | Nejc Habjan | 2022-08-04 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.8.0v3.8.0 | github-actions | 2022-08-04 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.7.0v3.7.0 | github-actions | 2022-07-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.6.0v3.6.0 | github-actions | 2022-06-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.5.0v3.5.0 | github-actions | 2022-05-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.4.0v3.4.0 | github-actions | 2022-04-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.3.0v3.3.0 | github-actions | 2022-03-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.2.0v3.2.0 | github-actions | 2022-02-28 | 1 | -1/+1 |
| | | |||||
| * | chore: release v3.1.1v3.1.1 | github-actions | 2022-01-28 | 1 | -1/+1 |
| | | |||||
| * | chore: rename `gitlab/__version__.py` -> `gitlab/_version.py`jlvillal/version_mv | John L. Villalovos | 2022-01-15 | 1 | -0/+6 |
| It is confusing to have a `gitlab/__version__.py` because we also create a variable `gitlab.__version__` which can conflict with `gitlab/__version__.py`. For example in `gitlab/const.py` we have to know that `gitlab.__version__` is a module and not the variable due to the ordering of imports. But in most other usage `gitlab.__version__` is a version string. To reduce confusion make the name of the version file `gitlab/_version.py`. | |||||
 |
index : delta/python-packages/gitlab.git | |
| github.com: gpocentek/python-gitlab.git |
| summaryrefslogtreecommitdiff |