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

Fix: Expense custom Field active flag #462

Merged
merged 2 commits into from
Nov 29, 2023
Merged

Conversation

ruuushhh
Copy link
Contributor

No description provided.

@ruuushhh ruuushhh self-assigned this Nov 29, 2023
Copy link

Tests Skipped Failures Errors Time
215 0 💤 0 ❌ 0 🔥 20.769s ⏱️

Copy link

Tests Skipped Failures Errors Time
215 0 💤 0 ❌ 0 🔥 21.491s ⏱️

Copy link

codecov bot commented Nov 29, 2023

Codecov Report

Merging #462 (ff1acfb) into master (512a6c8) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #462   +/-   ##
=======================================
  Coverage   95.12%   95.12%           
=======================================
  Files          49       49           
  Lines        4636     4636           
=======================================
  Hits         4410     4410           
  Misses        226      226           
Files Coverage Δ
apps/mappings/constants.py 100.00% <ø> (ø)
apps/mappings/tasks.py 96.07% <100.00%> (ø)

@ruuushhh ruuushhh added the deploy Triggers deployment of active branch to Staging label Nov 29, 2023
@NileshPant1999 NileshPant1999 changed the title Fix: Expense custome Field active flag Fix: Expense custom Field active flag Nov 29, 2023
Copy link

Tests Skipped Failures Errors Time
215 0 💤 0 ❌ 0 🔥 20.560s ⏱️

@ruuushhh ruuushhh merged commit 3ebce04 into master Nov 29, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy Triggers deployment of active branch to Staging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants