huggingchat/chat-ui · Input that makes Falcon-180B chat chat fail and never become active again

Below is the prompt that always fails the chat:

I will give you a list of commits. The commits can be multiline, so the delimiter I will use to indicate the end of a commit message is a line with multiple "equal" chars, like this: "=====".

These are commits we are about to deploy - basically it is a track of what happened in the git branch since previous successful deploy.

Upon successful deploy, we want to update the stakeholders about what new things were deployed, so we need to compose a message that lists all important things, new features, updates, etc from this list of commits.

However, we also want to exclude things that are not important and convey no meaning in the eyes of stakeholders. Here is the list of non-important things:

Merges: these are just byproduct of using git features. Example git commit messages: "Merge branch 'master' of example:webapp/bot", or "Merge branch 'f15_preview_tg_msgs' of example:webapp/bot into f15_preview_tg_msgs"
Duplicate messages. Yes, we also want to exclude duplicate messages, as this is also a case that can happen. For instance, there was a case when we committed 3 times with minor updates to the same thing, and we use the same commit message every single time: "Update FxMonitor.php".
Updates that are too broad. We want to exclude them too as they mean absolutely nothing to the stakeholders. For example, commit message "Fix UI" does not mean anything, so it is better to exclude it from the summary message. The only exception is if there iare no other interesting commits to include in the summary - if this is the case, and the generic message is the only meaningful update available, then you have no other option but to include it. Btw, another example of a commit message that is too broad and is better to exclude is "Code review feedback".

My input will be a list of commits, in some format that is output by git command line tool.

The final result, which is your output, is a simple text formatted as a bullet list of updates. Do not use html or json or markup or any other formatted text markup! Just use the plain text, bullet point character "■", and normal line breaks. Separate each item in the list that you generate with a blank line; in other words, there will always be a blank line before a ■ appears (except the beginning of the text, of course). We will use your output and send it to telegram as a plain text message, so simplicity and readability is the key.

Do not add any introduction or filler words or fillter sentences, greetings, etc - we are not emulating a standard chat here. What we need is the following scenario: we give you input as a list of commit messages, you give us output that we can send in Telegram. Also, we will make our CI/CD software call you via API, that is why it is important that your output is the final commits summary and nothing else and nothing extra - because it will go to the stakeholders directly.

Important: Your job is to extract only important messages/sentences, but not to rephrase them. You can either include some sentence in full as is, or exclude it, but you must not rephrase anything or shorten the text to make it more readable. It is important that we maintain nuances that are found in the commit messages, so your job is not to rewrite the message themselves, but rather to identify the important ones and include them (or part of them), as is, one to one, without rewriting, paraphrasing, using different languages, etc.

How to format lists found inside commit message: you may occasionally find that commit messages include internal lists themselves. For example:

<<< EXAMPLE
Any of the following would triggered the policy:

the product is found in at least one successful non-rejected order
(more policies can be added later)
<<< END EXAMPLE

In this case, you would want to use a double-dash for the internal list formatting. In this particular example, a dash is used for each list item, but you would replace a single dash by a double dash i.e. "--". This is to avoid applying any automatic markdown formatting.

How to format multiple paragraphs with lists inside commit message: you may occasionally find multiple paragraphs and internal lists combined in a single message. For example:

<<<EXAMPLE
Any of the following would triggered the policy:

the product is found in at least one successful non-rejected order
(more policies can be added later)

Considerable changes are any edits to the product name EXCEPT the following:

letter case change
adding/removing punctuation and/or spaces
<<<END EXAMPLE

If this happens, do not convert a non-list sentences into list sentences. For example, the sentence "Any of the following would triggered the policy:" is not an item list, so you must not prefix it with a double dash; it must remain a simple sentence. You must only convert formatting of internal list items into using double dashes, but not convert other content, like simple paragraphs or newlines.

Newlines: It is important that if you use a commit message in full, you must not delete newlines from it; you must preserve the existing newlines when using a commit message.

Delimiter: obviously, you must not include the delimiter equal signs "=====" in your commit messages.

Ordering: you are allowed to re-order the higher-level items that you generate in the order of detail and specificy, so that the more detailed and important and easier to understand commit messages come first, and the least specific come last. You are only allowed to re-order at a higher leve, i.e. where you use ■ - to list commit messages; but you cannot re-order anything inside the commit messages themselves; and certainly you cannot reorder items inside internal lists found inside commit messages.