From 969d3f99ec4c0b7fb518c5098ef2b6c8614b8065 Mon Sep 17 00:00:00 2001 From: Kyle Willmon Date: Thu, 21 Nov 2024 09:51:42 -0600 Subject: [PATCH 1/2] Explain the effect of current job on monitoring The current job concept is explained directly on the continuous monitoring page since this is where the impact is most clearly seen. --- docs/knowledge_base/continuous_monitoring.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/knowledge_base/continuous_monitoring.md b/docs/knowledge_base/continuous_monitoring.md index 92860a71..6b61aaed 100644 --- a/docs/knowledge_base/continuous_monitoring.md +++ b/docs/knowledge_base/continuous_monitoring.md @@ -4,10 +4,18 @@ Phylum Continuous Monitoring ensures the accuracy of package issue data without ## How It Works -The Phylum platform monitors for new issues that impact dependencies in your project and will re-run your policy when one is found. If that issue violates your policy, we will fire off any configured [notifications] and also unsuppress the package if you previously had it suppressed, so you can address the newly found issue. +The Phylum platform monitors for new issues that impact dependencies in your project's current job (see below for details) and will re-run your policy when one is found. If that issue violates your policy, we will fire off any configured [notifications] and also unsuppress the package if you previously had it suppressed, so you can address the newly found issue. [notifications]: ../knowledge_base/notifications.md +### Current job + +A project's current job is the latest job that has been submitted with the project's default label. The default label can be set "Preferences" tab of the project in the Phylum App or [with the Phylum CLI][project_update]. + +If no default label has been set, the project's current job will be the latest job submitted, regardless of label. + +[project_update]: https://docs.phylum.io/cli/commands/phylum_project_update + ## How to Activate No activation required! Continuous Monitoring is a default platform feature for all Phylum accounts. Phylum Pro users have the additional option to trigger [notifications] on new Continuous Monitoring violations. From 6b3b2bbe1fa85824ffea362549a702985d8efc60 Mon Sep 17 00:00:00 2001 From: Kyle Willmon Date: Thu, 21 Nov 2024 13:39:28 -0600 Subject: [PATCH 2/2] Apply code review suggestions --- docs/knowledge_base/continuous_monitoring.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/knowledge_base/continuous_monitoring.md b/docs/knowledge_base/continuous_monitoring.md index 6b61aaed..c3858168 100644 --- a/docs/knowledge_base/continuous_monitoring.md +++ b/docs/knowledge_base/continuous_monitoring.md @@ -8,12 +8,13 @@ The Phylum platform monitors for new issues that impact dependencies in your pro [notifications]: ../knowledge_base/notifications.md -### Current job +### Current Job -A project's current job is the latest job that has been submitted with the project's default label. The default label can be set "Preferences" tab of the project in the Phylum App or [with the Phylum CLI][project_update]. +A project's current job is the latest job that has been submitted with the project's default label. The default label can be set from the "Preferences" tab of the project in the [Phylum UI][phylum_ui] or [with the Phylum CLI][project_update]. If no default label has been set, the project's current job will be the latest job submitted, regardless of label. +[phylum_ui]: https://app.phylum.io [project_update]: https://docs.phylum.io/cli/commands/phylum_project_update ## How to Activate