Hello,

We have several JSON schema specifications and files that we can check with them as pre-commit check, but this is not yet checked. I think it is worth adding such checking.

• dev/provider.yaml.schema.json
• [chart/values.schema.json](https://github.com/apache/airflow/blob/master/chart/values.

Summary

What change needs making?

Add workflows.argoproj.io/cron-workflow, workflows.argoproj.io/workflow-template to the UI Labels autocomplete

For example,

Use Cases

When would you use this?

This will enable us to quickly filter all cronWorkflows or templat

Context
Currently, when prefect.tasks.shell.ShellTask is invoked with return_all=True, the shell task will not log the stdout through logger.debug.

This is defined in doc
https://docs.prefect.io/api/latest/tasks/shell.html#shelltask
and implement in the code.
https://github.com/PrefectHQ/prefect/blob/73fe1eb57945fc13bdd36b361a6a17c3f324b1ba/src/prefect/tasks/shell.py#L107-L111

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.

Currently, the repository name and repository location name are just displayed next to each other in the Dagit repository picker.

We should make it more obvious about which one is which. This would help expose the concept of repository locations to the user as well.

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