merge3#3
Open
mollysacks wants to merge 812 commits into
Open
Conversation
Add section for maintainers in contributor docs
Guarantee that CI builds docs the same way devs can locally.
Consolidate methods for building docs into noxfile
- Change title/header font to Lexend Deca - Include terms and conditions in copyright footer - Remove "Built with Sphinx" callout - Change top-left quadrant color to Tamr's Brilliant Blue - Set favicon to Tamr icon
...to distinguish from h2
Change doc styling
Avoids singletons and the class vs instance distinction
- Move types into _types package - Absorb aliases into _types/attribute.py module - Namepace attributes/attribute_type as attributes/type - Improve comments explaining forward references + recursive dependencies
Also, rename remaining subattribute to sub
Introduce the _types package
Hide beta module from users
Also, improved clarity of the beta error message
Simplified beta check
__init__.py files are used to control the interface exposed to the user and do not contain any logic. For now tamr_client/__init__.py also ignores other errors, but in the future this file should also only ignore F401 errors.
Ignore F401 flake8 error explicitly
Docs dependencies should be tracked in docs/requirements.txt for interop w/ RTD. The only dev task (aka nox session) that uses these dependencies is `docs`, so we can safely remove doc-only deps from pyproject.toml/poetry.lock .
Removes many deprecation warnings for build output.
Update checkout and setup-python actions to v2
Add functionality to get, initiate and cancel Tamr backups and restores
See https://www.conventionalcommits.org/en/v1.0.0/ . Note that `fetch-depth: 0` is necessary for `actions/checkout@v2` to checkout the entire git history, and not just the last commit.
Changelog is obsoleted by automated Github release notes. Also, remove references to the changelog. Also, simplify the Pull Request template. Fixes #387
Semantic release
With automated releases via semantic-release, there will be no need for release branches anymore.
See [semantic-release's authentication docs][1] and [Github Action's authentication docs][2] [1] https://semantic-release.gitbook.io/semantic-release/usage/ci-configuration#authentication [2] https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow
Fix semantic release
…a generator that is empty
TC: Fix record.stream to be a generator
…ot explicitly defined
TC: Add a catch-all project dataclass to handle project types not explicitly defined
The poetry docs explicitly warn against using pip for installation. See https://python-poetry.org/docs/#installing-with-pip. Instead, we'll use a Github Action tailor-made for installing poetry.
ci(release): do not use pip to install poetry
TC: Create dataset from DataFrame
Add ADR specifying policy on optimization of new features
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
↪️ Pull Request
💻 Examples
✔️ PR Todo
-devversion:[#<issue number>](<link to issue>) <change description>