This is an automated email from the ASF dual-hosted git repository.
ka94 pushed a change to branch issues/4762
in repository https://gitbox.apache.org/repos/asf/incubator-devlake.git
omit c8fad1aa7 feat: Rework scope_helper for compatiblity with Python and
adapt DeleteScope to it
add 00c5efffa fix: gitHub repos' url columns are empty (#5228)
add 887dc3d37 docs: clarify debug steps for change lead time (#5231)
add 88d7dfea8 [fix-5233]: Pagerduty MTTR computation fix (#5229)
new 26f5a7d2f feat: Rework scope_helper for compatiblity with Python and
adapt DeleteScope to it
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 (c8fad1aa7)
\
N -- N -- N refs/heads/issues/4762 (26f5a7d2f)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
backend/plugins/github/tasks/repo_convertor.go | 5 +-
backend/plugins/pagerduty/impl/impl.go | 1 +
.../plugins/pagerduty/tasks/incidents_converter.go | 6 ++
.../tasks/service_converter.go} | 55 ++++++++++---------
grafana/dashboards/DORADebug.json | 64 +++++++++++-----------
5 files changed, 70 insertions(+), 61 deletions(-)
copy backend/plugins/{teambition/tasks/project_convertor.go =>
pagerduty/tasks/service_converter.go} (63%)
