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

feat: fix repo #4

Merged
merged 1 commit into from
Jan 23, 2024
Merged

feat: fix repo #4

merged 1 commit into from
Jan 23, 2024

Conversation

ron-gal
Copy link
Contributor

@ron-gal ron-gal commented Jan 23, 2024

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@ron-gal ron-gal requested a review from a team as a code owner January 23, 2024 18:27
Copy link

conventional-commit-lint-gcf bot commented Jan 23, 2024

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

@averikitsch averikitsch merged commit f6c1cda into main Jan 23, 2024
6 of 7 checks passed
@averikitsch averikitsch deleted the repo_fix branch January 23, 2024 19:15
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.

2 participants