mattermost-mobile/.github/actions
Rahim Rahman abb526cf83
ci(MM-63199): code coverage tracking (#8642)
* ci(MM-63199): code coverage tracking

* try to download existing coverage file

* read coverage

* add token

* use github.token instead

* passing github token

* github_token passing from workflow

* remove download

* re-add download

* wrong param

* try download all artifacts

* add run-id so to retrieve with download later

* remove read coverage temp

* use run-id to download

* put files into current-coverage

* using last run id

* temporary comment

* can retrieve last run id?

* remove hard-coding

* echo into github_env vs export

* comparing new and old

* comparison improvement

* post to github

* fix coverage text

* refactor to main from current-coverage

* formatting changes

* fix missing content

* small tweaking

* showing the Warning to make sure

* formatting

* remove +

* checking to see if the error shows via echo

* revert the change to error

* separate to a new file

* comment the actual test for now

* prep node deps

* only run certain things on main

* trying cache-hit

* real trying cache-hit

* testing to make sure cache-run-id runs

* save-always true

* save-always deprecated

* let's try different strategy

* add key

* restore-key adding a -

* only perform on `main`

* only run on main or if its a PR

* coverage_threshold

* remove comments

* add total

* removing unneeded comments

* calculate total

* run test in `release-*` only

* making sure that only PR will run

* only do more steps if upload-coverage successful

* trying thollander/actions-comment-pull-request

* using diff way to comment.

* comment on how things work

* testing to trigger warning and see if comment is updated vs new comment

* omit echo messages

* see if giving github token would work.

* wrong use of param

* try without github token

* adding a very simple change to see where it lands

* using cache hit instead.

* creating the cache again.  how did i lose it?

* revert back

* cache-hit might be off

* debug

* debug with failing cache restoration

* check for run-id.txt instead

* all into action

* missing "

* remove unneeded actions
* change threshold to 0.5

* relative time

* skeptical about date formatting

* revert back to the threshold trigger

* below 80% total coverage threshold

* only show one error/warning at  time.

* testing if the coverage drop below 80

* debug output

* add Reset Test Coverage label use

* try using contains vs direct comparsion

* remove the label checker

* temp change

* ooops

* revert back

* let's post before exiting

* consistency

* total coverage threshold reset to 80%
2025-03-14 13:21:25 -06:00
..
bandwidth-throttling test: mitmproxy + low bandwidth + automated QA using detox (#8202) 2024-10-14 07:56:52 -06:00
generate-specs Add ability to run detox tests on Android (#8553) 2025-02-14 01:26:53 +05:30
prepare-android-build Bump the github-actions-updates group across 5 directories with 6 updates (#8613) 2025-02-19 14:28:06 +02:00
prepare-ios-build Bump the github-actions-updates group across 5 directories with 6 updates (#8613) 2025-02-19 14:28:06 +02:00
prepare-low-bandwidth test: mitmproxy + low bandwidth + automated QA using detox (#8202) 2024-10-14 07:56:52 -06:00
prepare-mobile-build Bump the github-actions-updates group across 5 directories with 6 updates (#8613) 2025-02-19 14:28:06 +02:00
prepare-node-deps fix(MM-62375): OutOfMemoryError issue with better catching (#8622) 2025-02-28 10:16:55 -07:00
start-proxy test: mitmproxy + low bandwidth + automated QA using detox (#8202) 2024-10-14 07:56:52 -06:00
test ci(MM-63199): code coverage tracking (#8642) 2025-03-14 13:21:25 -06:00
test-coverage ci(MM-63199): code coverage tracking (#8642) 2025-03-14 13:21:25 -06:00