Skip to content
New issue

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

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

Already on GitHub? # to your account

Feature/attendance fateme #34

Merged
merged 14 commits into from
Mar 16, 2023

Conversation

fatemetardasti96
Copy link
Contributor

Checklist for your PR

  • please start with a draft PR and mark it as ready for review when you are confident that your implementation works as expected.
  • add a changelog entry in CHANGELOG.md with a link to this PR.
  • make sure that all tests pass and add new test functions if your code is not covered by existing tests. Please use mock tests when network requests are required.
  • let someone review & approve your code, make changes where necessary.

Hints

  • name your branches accordingly: use the prefixes bugfix/, feature/, or release/ and then a short title for your PR in kebab-case (lowercase words separated with dashes), e.g. feature/my-awesome-feature.
  • Please make sure that pre-commit hooks are enabled on your system to avoid common mistakes before you make a commit.
  • feel free to delete this template and replace it with your own description of the PR.

@fatemetardasti96 fatemetardasti96 marked this pull request as ready for review March 16, 2023 08:40
@fatemetardasti96 fatemetardasti96 merged commit d3c32bd into feature/attendances Mar 16, 2023
@fatemetardasti96 fatemetardasti96 deleted the feature/attendance-fateme branch March 16, 2023 15:55
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant