This is an automated email from the ASF dual-hosted git repository.
ka94 pushed a change to branch issues/5939
in repository https://gitbox.apache.org/repos/asf/incubator-devlake.git
omit 6d926bf33 refactor: removed temporal support
add 62a1e93a2 feat(pagerduty): add pagerduty priority as issue severity
(#6126)
add 0039b6b29 refactor: removed temporal support
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (6d926bf33)
\
N -- N -- N refs/heads/issues/5939 (0039b6b29)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
backend/plugins/pagerduty/models/incident.go | 1 +
.../20230920_add_incident_priority.go} | 26 +++++++++------------
.../pagerduty/models/migrationscripts/register.go | 1 +
backend/plugins/pagerduty/models/raw/incidents.go | 27 +++++++++++-----------
.../plugins/pagerduty/tasks/incidents_converter.go | 1 +
.../plugins/pagerduty/tasks/incidents_extractor.go | 3 +++
6 files changed, 30 insertions(+), 29 deletions(-)
copy backend/plugins/{zentao/models/migrationscripts/20230627_add_task_left.go
=> pagerduty/models/migrationscripts/20230920_add_incident_priority.go} (66%)
