Show a warning annotation when "master" branch usage is detected

[stronk7]

That way, both the web UI and the email from GitHub will show the recommendation about to move to the new "main" branch.

Also, unrelated, exclude some unreachable code from code coverage analysis.

Here there is an example to show how the annotation looks like (at the bottom):

https://github.com/stronk7/moodle-plugin-ci/actions/runs/7812729398

Note that an unrelated 2nd commit has been added about to try to keep Travis working, because it has started to fail recently (maybe they changed the PostgreSQL ports again, grrr).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8124fe7) 84.77% compared to head (28605ed) 85.10%.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #270      +/-   ##
============================================
+ Coverage     84.77%   85.10%   +0.33%     
- Complexity      720      722       +2     
============================================
  Files            75       75              
  Lines          2226     2216      -10     
============================================
- Hits           1887     1886       -1     
+ Misses          339      330       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stronk7]

Side note, I'm not sure what's going with Travis since 1-2 weeks ago, maybe they are upgrading their environments because all our PostgreSQL related tests are failing with different errors (not package available, not running @ port xxxx, ...).

I'll take a look to that, but apart from this issue, just sharing why it's failing.

Ciao :-)

[stronk7]

Other than that, I think this is ready for review as far as it seems to be working ok. Feel free to suggest a better wording or whatever (I'm not good there!).

Ciao :-)

[stronk7]

Ok,

confirmed, Travis has changed PostgreSQL default port from the exceptional 5432 that it had since last year to the usual 5433 that they have for all versions since v10.

This run (that uses the 2nd commit added here) is now running ok:

https://app.travis-ci.com/github/moodlehq/moodle-plugin-ci/builds/268805831

So, if we get everything green, we can go with this. 2 issues fixed in 1 PR.

Ciao :-)

[stronk7]

Grrr, it's flip.flopping (the PostgreSQL 13 port). Last run failed with the change back to 5433. And now it's showing 5432 again:

$ ls -al /var/run/postgres*
total 8
drwxrwsr-x  3 postgres postgres  120 Feb  8 15:42 .
drwxr-xr-x 34 root     root     1100 Feb  8 15:42 ..
drwxr-s---  2 postgres postgres   80 Feb  8 15:42 13-main.pg_stat_tmp
-rw-r--r--  1 postgres postgres    5 Feb  8 15:42 13-main.pid
srwxrwxrwx  1 postgres postgres    0 Feb  8 15:42 .s.PGSQL.5432
-rw-------  1 postgres postgres   69 Feb  8 15:42 .s.PGSQL.5432.lock

(yesterday it was showing 5433, that's the reason I added the 2nd commit)

I'm going to switch back to 5432, removing the second commit in this PR and doing a few more tests... grrr.

Ciao :-)

[stronk7]

Ok, back to port 5432 (the original one). Seems to be working now. What a waste of time!

[kabalin]

LGTM 👍

[stronk7]

Thanks Mr. @kabalin !