mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
67 lines
1.5 KiB
Markdown
67 lines
1.5 KiB
Markdown
## What type of PR is this? (check all applicable)
|
|
|
|
- [ ] Refactor
|
|
- [ ] Feature
|
|
- [ ] Bug Fix
|
|
- [ ] Optimization
|
|
- [ ] Documentation Update
|
|
- [ ] Community Node Submission
|
|
|
|
|
|
## Have you discussed this change with the InvokeAI team?
|
|
- [ ] Yes
|
|
- [ ] No, because:
|
|
|
|
|
|
## Have you updated all relevant documentation?
|
|
- [ ] Yes
|
|
- [ ] No
|
|
|
|
|
|
## Description
|
|
|
|
|
|
## Related Tickets & Documents
|
|
|
|
<!--
|
|
For pull requests that relate or close an issue, please include them
|
|
below.
|
|
|
|
For example having the text: "closes #1234" would connect the current pull
|
|
request to issue 1234. And when we merge the pull request, Github will
|
|
automatically close the issue.
|
|
-->
|
|
|
|
- Related Issue #
|
|
- Closes #
|
|
|
|
## QA Instructions, Screenshots, Recordings
|
|
|
|
<!--
|
|
Please provide steps on how to test changes, any hardware or
|
|
software specifications as well as any other pertinent information.
|
|
-->
|
|
|
|
## Merge Plan
|
|
|
|
<!--
|
|
A merge plan describes how this PR should be handled after it is approved.
|
|
|
|
Example merge plans:
|
|
- "This PR can be merged when approved"
|
|
- "This must be squash-merged when approved"
|
|
- "DO NOT MERGE - I will rebase and tidy commits before merging"
|
|
- "#dev-chat on discord needs to be advised of this change when it is merged"
|
|
|
|
A merge plan is particularly important for large PRs or PRs that touch the
|
|
database in any way.
|
|
-->
|
|
|
|
## Added/updated tests?
|
|
|
|
- [ ] Yes
|
|
- [ ] No : _please replace this line with details on why tests
|
|
have not been included_
|
|
|
|
## [optional] Are there any post deployment tasks we need to perform?
|