| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes #1764
|
|\
| |
| | |
chore: add .env as a file that search tools should not ignore
|
| |
| |
| |
| |
| |
| | |
The `.env` file was not set as a file that should not be ignored by
search tools. We want to have the search tools search any `.env`
files.
|
|/ |
|
| |
|
|\
| |
| | |
feat: add support for `squash_option` in Projects
|
|/
|
|
|
|
|
| |
There is an optional `squash_option` parameter which can be used when
creating Projects and UserProjects.
Closes #1744
|
|\
| |
| | |
feat(cli): do not require config file to run CLI
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BREAKING CHANGE: A config file is no longer needed to run
the CLI. python-gitlab will default to https://gitlab.com
with no authentication if there is no config file provided.
python-gitlab will now also only look for configuration
in the provided PYTHON_GITLAB_CFG path, instead of merging
it with user- and system-wide config files. If the
environment variable is defined and the file cannot be
opened, python-gitlab will now explicitly fail.
|
|\ \
| |/
|/| |
chore: add Python 3.11 testing
|
|/
|
|
|
|
|
|
|
|
| |
Add a unit test for Python 3.11. This will use the latest version of
Python 3.11 that is available from
https://github.com/actions/python-versions/
At this time it is 3.11.0-alpha.2 but will move forward over time
until the final 3.11 release and updates. So 3.11.0, 3.11.1, ... will
be matched.
|
| |
|
|
|
|
| |
It is not yet available upstream.
|
| |
|
| |
|
|\
| |
| | |
chore: add get() methods for GetWithoutIdMixin based classes
|
| |
| |
| |
| |
| |
| |
| | |
Add the get() methods for the GetWithoutIdMixin based classes.
Update the tests/meta/test_ensure_type_hints.py tests to check to
ensure that the get methods are defined with the correct return type.
|
|\ \
| |/
|/| |
feat: package file delete on package file object
|
|/ |
|
|\
| |
| | |
chore: github workflow: cancel prior running jobs on new push
|
|/
|
|
|
| |
If new new push is done to a pull-request, then cancel any already
running github workflow jobs in order to conserve resources.
|
|\
| |
| | |
chore: add running unit tests on windows/macos
|
| |
| |
| |
| |
| | |
Add running the unit tests on windows-latest and macos-latest with
Python 3.10.
|
|\ \
| |/
|/| |
chore: fix pylint error "expression-not-assigned"
|
|/
|
|
|
|
|
|
| |
Fix pylint error "expression-not-assigned" and remove check from the
disabled list.
And I personally think it is much more readable now and is less lines
of code.
|
|\
| |
| | |
chore: add initial pylint check
|
| |
| |
| |
| |
| |
| |
| | |
https://github.com/pre-commit/mirrors-mypy/blob/master/.pre-commit-hooks.yaml
Sets some default args which seem to be interfering with things. Plus
we set all of our args in the `pyproject.toml` file.
|
| |
| |
| |
| |
| | |
If .pre-commit-config.yaml or .github/workflows/pre_commit.yml are
updated then run pre-commit.
|
|/
|
|
|
|
| |
Initial pylint check is added. A LONG list of disabled checks is also
added. In the future we should work through the list and resolve the
errors or disable them on a more granular level.
|
|\
| |
| | |
Enable more strict mypy checking
|
| |
| |
| |
| | |
Enable 'warn_redundant_casts'for mypy and resolve one issue.
|
|/
|
|
|
| |
Enable the subset of the 'mypy --strict' options that work with no
changes to the code.
|
| |
|
|\
| |
| | |
docs: only use type annotations for documentation
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
chore: attempt to be more informative for missing attributes
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A commonly reported issue from users on Gitter is that they get an
AttributeError for an attribute that should be present. This is often
caused due to the fact that they used the `list()` method to retrieve
the object and objects retrieved this way often only have a subset of
the full data.
Add more details in the AttributeError message that explains the
situation to users. This will hopefully allow them to resolve the
issue.
Update the FAQ in the docs to add a section discussing the issue.
Closes #1138
|
|\ \
| |/
|/| |
refactor: explicitly import gitlab.const values into top-level namespace
|
| |
| |
| |
| | |
Update the docs to use gitlab.const to access constants.
|
| |
| |
| |
| |
| | |
Have code use constants from the gitlab.const module instead of from
the top-level gitlab module.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are planning on adding enumerated constants into gitlab/const.py,
but if we do that than they will end up being added to the top-level
gitlab namespace. We really want to get users to start using
`gitlab.const.` to access the constant values in the future.
Add the currently defined constants to a list that should not change.
Use a module level __getattr__ function so that we can deprecate
access to the top-level constants.
Add a unit test which verifies we generate a warning when accessing
the top-level constants.
|
|\
| |
| | |
test(cli): improve basic CLI coverage
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
chore: remove pytest-console-scripts specific config
|