bms TUI page, database size tracking / state table purging, automated exporting #82
Conversation
Signed-off-by: Andrew Carlisle <161524638+AndrewCarlisleECE@users.noreply.github.com>
📦 Dependency Check 📦Did you add a new dependency? If so, justify why it must be added. Dependencies adding functionality that could reasonably be written by the YJSP team should be rejected, as well as those that are not actively maintained. |
🚀 Verification Evidence 🚀How do you know that your changes work? Reply to this comment with with specific evidence that all functionality added or changed in this pull request is working as expected. |
🧪 Regression Testing 🧪What have you done to ensure that future regressions of the functionality added or changed in this pull request are caught before being deployed to a production environment? This can include unit, isolation, and/or integration tests, or manual procedures if necessary. |
📝 Documentation 📝Where is this work being tracked, and is the ticket describing these changes up to date? Reply with a link to the ticket and all other documentation such as RFCs and PDRs. The reviewer(s) must also confirm that all documentation is up to date. |
🚀 Verification Evidence 🚀How do you know that your changes work? Reply to this comment with with specific evidence that all functionality added or changed in this pull request is working as expected. |
🧪 Regression Testing 🧪What have you done to ensure that future regressions of the functionality added or changed in this pull request are caught before being deployed to a production environment? This can include unit, isolation, and/or integration tests, or manual procedures if necessary. |
📝 Documentation 📝Where is this work being tracked, and is the ticket describing these changes up to date? Reply with a link to the ticket and all other documentation such as RFCs and PDRs. The reviewer(s) must also confirm that all documentation is up to date. |
📦 Dependency Check 📦Did you add a new dependency? If so, justify why it must be added. Dependencies adding functionality that could reasonably be written by the YJSP team should be rejected, as well as those that are not actively maintained. |
2 participants
No description provided.