feat: add a trigger column to the archive table#1732
Merged
Conversation
… was created by the scheduler or by the user manually
14 tasks
m3nu
approved these changes
Jun 23, 2023
Contributor
|
Tested locally and worked as advertised. Thanks for the patience and contribution. 🙏 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a "trigger" column to the archive table that shows whether an archive was created by the scheduler or by the user manually.
To cover:
Related Issue
Part of #1723
Motivation and Context
Easier to differentiate between schedule and user created archives.
How Has This Been Tested?
Created 3 archives with the scheduler and manually.
Screenshots (if appropriate):
Types of changes
Checklist:
I provide my contribution under the terms of the license of this repository and I affirm the Developer Certificate of Origin.