Initial PR & build pipeline definitions #27
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds YAML definitions for 1) Public PR pipelines via GitHub actions (python-package.yml) and 2) ADO-side CI and validation (ci-pr.yaml). Tries to follow the same organization as https://github.com/microsoft/Agents-for-python.
With these in place, next step will be to add internal YAML definition on the ADO side to build/validate/publish.
Copilot summary:
This pull request establishes foundational infrastructure for the project, including CI/CD pipelines, development tooling, and initial metadata. The most important changes are the addition of GitHub Actions and Azure DevOps pipelines for automated testing, development dependency management, project metadata updates, and documentation of release notes and changelog procedures.
Continuous Integration & Testing
.github/workflows/python-package.yml) for automated testing and linting on pushes and pull requests tomain, using Python 3.12 and standard tools (black,flake8,pytest)..azdo/ci-pr.yaml) that mirrors the GitHub Actions workflow for consistency, also using Python 3.12.Development Tooling
dev_dependencies.txtfile listing development dependencies such aspytest,black,flake8, and build tools for local and CI use..flake8configuration file to enforce code style and complexity limits, specifying exclusions for common build and environment folders.Project Metadata & Documentation
pyproject.tomlto refine project metadata: renamed the package todataverse-client-python, updated author/license info, added classifiers, and set up project URLs.CHANGELOG.mdfile following the Keep a Changelog format, documenting initial features and providing a template for future releases.__version__module and exposed version information in the package’s public API (src/dataverse_sdk/__init__.py,src/dataverse_sdk/__version__.py). [1] [2]