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

Remove not using imported classes and packages in the source file. #3836

Merged
merged 6 commits into from May 12, 2023

Conversation

arturobernalg
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • [X ] Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Remove not using imported classes and packages in the source file.

@nvoxland
Copy link
Contributor

nvoxland commented Mar 8, 2023

Initial/Pre-Review Thoughts

Does not actually impact functionality, just compilation so as long as it's only imports then "still compiles" is all the test that's really needed.

Questions I have:

  • None

Potential risks:

  • None

What could make the full review difficult:

  • Nothing

@MalloD12 MalloD12 self-assigned this Mar 31, 2023
@MalloD12 MalloD12 self-requested a review March 31, 2023 21:07
@MalloD12 MalloD12 changed the base branch from master to 1_9 April 1, 2023 14:27
@MalloD12 MalloD12 changed the base branch from 1_9 to master April 1, 2023 14:27
@MalloD12 MalloD12 added sprint2023-48 SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions labels Apr 1, 2023
Copy link
Contributor

@MalloD12 MalloD12 left a comment

Choose a reason for hiding this comment

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

Approved.

Review and testing results:

Changes look good to me. Integration tests were failing, but it was due some SHOW_SUMMARY missing changes I added to fix these tests. Functional tests are failing because of the same reason (not related with this PR). I'll investigate that separately with the team.

Things to be aware of:

  • None

Things to worry about:

  • None

@MalloD12 MalloD12 added SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions and removed SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions labels Apr 3, 2023
@MalloD12 MalloD12 added SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions and removed SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions labels Apr 20, 2023
@filipelautert filipelautert merged commit 45bee28 into liquibase:master May 12, 2023
32 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions sprint2023-48 TypeTechDebt
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

5 participants