Refine no-force-push (#12993)

* Refine no-force-push

* Tone down, tone up.

---------

Co-authored-by: Subhramit Basu <subhramit.bb@live.in>

Author: koppor

.github/ghprcomment.yml

@@ -88,10 +88,13 @@
 - jobName: no-force-push
   always: true
   message: >
-    Do not force-push!
-    Force pushing is a very bad practice when working together on a project (mainly because it is [not supported well by GitHub itself](https://github.com/orgs/community/discussions/3478)).
+    Hey, we noticed that you **force-pushed** your changes.
+    Force pushing is a bad practice when working together on a project (mainly because it is [not supported well by GitHub itself](https://github.com/orgs/community/discussions/3478)).
     Commits are lost and comments on commits lose their context, thus making it harder to review changes.
     At the end, all commits will be [squashed](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits) anyway before being merged into the `main` branch.
+
+
+    In future, **please avoid that**. For now, you can continue working.
 - jobName: 'Conflicts with target branch'
   message: >
     Your pull request conflicts with the target branch.