-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into DAT-10093
- Loading branch information
Showing
150 changed files
with
4,868 additions
and
1,460 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,64 +1,38 @@ | ||
<!--- This environment context section helps us quickly review your PR. | ||
Please take a minute to fill-out this information. --> | ||
## Environment | ||
## Impact | ||
|
||
**Liquibase Version**: | ||
|
||
**Liquibase Integration & Version**: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.> | ||
|
||
**Liquibase Extension(s) & Version**: | ||
|
||
**Database Vendor & Version**: | ||
|
||
**Operating System Type & Version**: | ||
|
||
## Pull Request Type | ||
|
||
<!--- What types of changes does your code introduce? | ||
Put an `x` in all the boxes that apply: | ||
If this PR fixes an existing GH issue, edit the next line to add "closes #XXXX" to auto-link. | ||
If this PR fixes an existing CORE Jira issue, note that as well, although there will be no auto-linking. --> | ||
- [ ] Bug fix (non-breaking change which fixes an issue.) | ||
- [ ] Enhancement/New feature (non-breaking change which adds functionality) | ||
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> | ||
- [ ] Bug fix (non-breaking change which fixes expected existing functionality) | ||
- [ ] Enhancement/New feature (adds functionality without impacting existing logic) | ||
- [ ] Breaking change (fix or feature that would cause existing functionality to change) | ||
|
||
## Description | ||
|
||
A clear and concise description of the issue being addressed. Additional guidance [here](https://liquibase.jira.com/wiki/spaces/LB/pages/1274904896/How+to+Contribute+Code+to+Liquibase+Core). | ||
- Describe the actual problematic behavior. | ||
A clear and concise description of the change being made. | ||
|
||
- Introduce what was/will be done in the title | ||
- Titles show in release notes and search results, so make them useful | ||
- Use verbs at the beginning of the title, such as "fix", "implement", "improve", "update", and "add" | ||
- Be specific about what was fixed or changed | ||
- Good Example: `Fix the --should-snapshot-data CLI parameter to be preserved when the --data-output-directory property is not specified in the command.` | ||
- Bad Example: `Fixed --should-snapshot-data` | ||
- If there is an existing issue this addresses, include "Fixes #XXXX" to auto-link the issue to this PR | ||
- If there is NOT an existing issue, consider creating one. | ||
- In general, issues describe wanted change from an end-user perspective and PRs describe the technical change. | ||
- If this change is very small and not worth splitting off an issue, include `Steps To Reproduce`, `Expected Behavior`, and `Actual Behavior` sections in this PR as you would have in the issue. | ||
- Describe what users need and how the fix will affect them | ||
- Describe how the code change addresses the problem | ||
- Ensure private information is redacted. | ||
|
||
## Steps To Reproduce | ||
|
||
List the steps to reproduce the behavior. | ||
- Please be precise and ensure private information is redacted | ||
- Include things like | ||
- Files used - sql scripts, changelog file(s), property file(s), config files, POM Files | ||
- Exact commands used - CLI, maven, gradle, spring boot, servlet, etc. | ||
## Things to be aware of | ||
|
||
## Actual Behavior | ||
A clear and concise description of what happens in the software **before** this pull request. | ||
- Include console output if relevant | ||
- Include log files if available. | ||
- Describe the technical choices you made | ||
- Describe impacts on the codebase | ||
|
||
## Expected/Desired Behavior | ||
A clear and concise description of what happens in the software **after** this pull request. | ||
## Things to worry about | ||
|
||
## Screenshots (if appropriate) | ||
If applicable, add screenshots to help explain your problem. | ||
- List any questions or concerns you have with the change | ||
- List unknowns you have | ||
|
||
## Additional Context | ||
Add any other context about the problem here. | ||
|
||
## Fast Track PR Acceptance Checklist: | ||
<!--- Completing these speeds up the acceptance of your pull request --> | ||
<!--- Put an `x` in all the boxes that apply. --> | ||
<!--- If you're unsure about any of these, just ask us in a comment. We're here to help! --> | ||
- [ ] Build is successful and all new and existing tests pass | ||
- [ ] Added [Unit Test(s)](https://liquibase.jira.com/wiki/spaces/LB/pages/1274937609/How+to+Write+Liquibase+Core+Unit+Tests) | ||
- [ ] Added [Integration Test(s)](https://liquibase.jira.com/wiki/spaces/LB/pages/1276608569/How+to+Write+Liquibase+Core+Integration+Tests) | ||
- [ ] Added [Test Harness Test(s)](https://github.com/liquibase/liquibase-test-harness/pulls) | ||
- [ ] Documentation Updated | ||
|
||
## Need Help? | ||
Come chat with us in the [Liquibase Forum](https://forum.liquibase.org/). | ||
Add any other context about the problem here. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
liquibase-core/src/main/java/liquibase/change/core/CreateProcedureChange.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
liquibase-core/src/main/java/liquibase/change/core/CreateViewChange.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.