Description

The PR #12023 added consistency check for documentation and setup.py. However few packages need additional description:

• pagerduty
• plexus
• sentry
• singularity
• tableau
• virtualenv

This is a great "good-first-issue"

Use case / motivation

Descriptions should be complete.

Summary

I expect CLI docs to tell end user differences between argo terminate and argo stop intentions and its expected behavior. I found none.

Diagnostics

What Kubernetes provider are you using?
AWS
What version of Argo Workflows are you running?
2.16

**Message from the

Description

Recently, a task_run_name parameter was added to the task constructors, and documentation was written on how to dynamically set task Run Names dynamically based on inputs.

At runtime, Prefect automatically populates kwargs with raw inputs and also prefect context:
https://github.com/PrefectHQ/prefect/blob/1bbefb71

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it