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

[TM-617, 626, 627, 658] feat: add tree restoration controller and export csv #237

Merged

Conversation

@cesarLima1 cesarLima1 changed the title Feat/tm 617/626/627/658 tree restoration and export [TM-617, 626, 627, 658] feat: add tree restoration controller and export csv May 28, 2024
@cesarLima1 cesarLima1 requested a review from roguenet June 4, 2024 19:29
Base automatically changed from feat/TM-621_dashboard_jobs_created to staging June 6, 2024 15:25
@@ -23,6 +23,7 @@
use App\Models\V2\User;
use App\Models\V2\Workdays\Workday;
use App\Models\V2\Workdays\WorkdayDemographic;
use App\StateMachines\ReportStatusStateMachine;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect the linter will complain about this once it has a chance to run. Once the conflicts with base branch are cleared and the tests run successfully, I think this is ready to approve.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@roguenet the test has passed after resolving merging issues.

@cesarLima1 cesarLima1 merged commit d07e18b into staging Jun 6, 2024
1 check passed
@cesarLima1 cesarLima1 deleted the feat/TM-617/626/627/658_tree_restoration_and_export branch June 6, 2024 19:35
egrojMonroy pushed a commit that referenced this pull request Nov 1, 2024
…tion_and_export

[TM-617, 626, 627, 658] feat: add tree restoration controller and export csv
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.

3 participants