Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump lxml #469

Merged
merged 1 commit into from
Apr 12, 2024
Merged

build(deps): bump lxml #469

merged 1 commit into from
Apr 12, 2024

Conversation

satterly
Copy link
Member

Description
A clear and concise description of why this change is necessary.

Fixes # (issue)

Changes
Include a brief summary of changes...

  • change 1
  • change 2
  • change 3

Screenshots
If it's a UI change add screenshots to demonstrate changes.

Checklist

  • Pull request is limited to a single purpose
  • Code style/formatting is consistent
  • All existing tests are passing
  • Added new tests related to change
  • No unnecessary whitespace changes

Collaboration
When a user creates a pull request from a fork that they own, the user
generally has the authority to decide if other users can commit to the
pull request's compare branch. If the pull request author wants greater
collaboration, they can grant maintainers of the upstream repository
(that is, anyone with push access to the upstream repository) permission
to commit to the pull request's compare branch

See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

@satterly satterly merged commit eb2ce8c into master Apr 12, 2024
4 checks passed
@satterly satterly deleted the deps-lxml branch April 12, 2024 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant