Skip to content

Irrigation/General Observation report and gatekeeper integration#15

Closed
JoleVLF wants to merge 10 commits intomainfrom
irrigation-report
Closed

Irrigation/General Observation report and gatekeeper integration#15
JoleVLF wants to merge 10 commits intomainfrom
irrigation-report

Conversation

@JoleVLF
Copy link
Copy Markdown
Contributor

@JoleVLF JoleVLF commented Jan 10, 2025

No description provided.

@JoleVLF JoleVLF changed the title Irrigation report Irrigation report and gatekeeper integration Jan 10, 2025
@JoleVLF JoleVLF changed the title Irrigation report and gatekeeper integration Irrigation/General Observation report and gatekeeper integration Jan 28, 2025
@JoleVLF JoleVLF marked this pull request as ready for review January 28, 2025 13:53
@JoleVLF JoleVLF requested review from fedjo, nikoskal and prske January 30, 2025 10:36
Copy link
Copy Markdown
Collaborator

@fedjo fedjo left a comment

Choose a reason for hiding this comment

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

Hi @JoleVLF This PR is enormous it is impossible to be reviewed. I suggest you break it in small PRs like

Irrigation report
GO report
GK integration

It would also be nice if the PR is big to add a small description to your PRs so reviewers what to expect

@JoleVLF
Copy link
Copy Markdown
Contributor Author

JoleVLF commented Feb 11, 2025

@fedjo It would be difficult to do separating this PRs because commits are tight connected. Also PR is big because 10 files are deleted (unused).

Also one commit is connected to another (fix previous work) so cherry pick this would not be good idea

@fedjo
Copy link
Copy Markdown
Collaborator

fedjo commented Feb 11, 2025

@fedjo It would be difficult to do separating this PRs because commits are tight connected. Also PR is big because 10 files are deleted (unused).

Also one commit is connected to another (fix previous work) so cherry pick this would not be good idea

Ahhh :-/ , I do understand. But this does not change that the PR will take ages to be reviewed (40 file changes). Also the bigger the PR the more prone to future errors because something the reviewer may miss. This will create bugfixes etc...

Maybe cherry-picking is not a good idea but since you know the changes it is easier to add them to separate PRs and create new commits.

@JoleVLF
Copy link
Copy Markdown
Contributor Author

JoleVLF commented Feb 11, 2025

@fedjo I will do my best, I created this as draft 2 months ago and requests changed, and one change followed another..
Anyway, I will try to do that

@JoleVLF JoleVLF closed this Feb 11, 2025
fedjo pushed a commit that referenced this pull request Dec 16, 2025
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.

4 participants