Additionally it would be good to override status check name and URL

As the status context fields from Harness to GitHub are currently being truncated to the pattern of the first 30 characters from the <pipeline_identifier>, the first thirty characters of the <stage_identifier> (where if either exceed 30 characters they are truncated to 27 and have three periods inserted), to accommodate field length limitations; likewise, the Description field in those same status messages are limited to 140 characters fitting:

"Execution status of Pipeline - <pipeline_identifier> (execution_ID) Stage - <stage_identifier> was SUCCEEDED"

This request is that Harness

pre-generate the max length status description at pipeline save/pipeline run-time, and produce some sort of a warning that the status description will need to be truncated, and then to consistently produce status messages that won't exceed GitHub's limitations (whether by truncating the identifiers as done for the status context, or by some other truncation, up through just returning a warning for the description field that it's 'truncated for run <executionid>').

This behaviour is critical to being able to reliably use Harness CI statuses and GitHub rulesets to properly quality-gate merges in Github.

Failing that, if Harness were to expose the actual templating pattern being used for generating the message that's erroring, allowing the user to edit/override the pattern with jexl expressions, then it would be possible for to construct rules/patterns to comply.

Currently we are restricted to using the pattern "pipelinename-stagename" to identify the links to tests/builds associated with a PR (Bitbucket). This can lead to a great deal of confusion if a PR has multiple test pipelines. In Jenkins, we are able to customize these titles using the Bitbucket Pullrequest Builder Plugin (see attached screenshot and this link for the details: https://github.com/jenkinsci/bitbucket-pullrequest-builder-plugin). Can the same capability be enabled in Harness CI?