eclipse-thingweb / .eclipsefdn Goto Github PK

We recently merged #14 to setup branch protection rules for node-wot.
Some comments/concerns based on eclipse-thingweb/node-wot#1240

• Approvals need to come from 2 team members (approvals from externals like @Kaz040 in PR eclipse-thingweb/node-wot#1240 do not work, which is somewhat okay, but see next point...)
• No way to overrule the protection (might be problematic in some cases if we need to merge a PR quickly)
  

I am not sure anymore whether this setting "as is" is very useful/practical...

@egekorkan @JKRhb @relu91

The Security Team at the EF would like to assist your project by enhancing their security posture by applying basic branch protection rules for all the repositories of this Github Organization. To do that, we will walk through you the diverse options available, ensuring you can effortlessly you can create PRs that suit your need.

Hi there :)

For dart_wot and other repositories, we are using codecov for displaying code coverage information. Recently, I noticed that the CODECOV_TOKEN secret that was defined before moving dart_wot to the Thingweb organization apparently hasn't been updated – or rather: there is now only a sequence of stars in the otterdog configuration file, supposedly indicating that it existed before:

What would be the process of updating this secret? Apparently, if there is no (valid?) token defined, you get rate-limited at some point, so adding it back to the repository would be a nice thing to have, I think.

I have realized at #3 that we have https://eclipse-thingweb.github.io/.eclipsefdn/ . @netomi can we add it as "homepage" of this repo? Also, does this repo need its own config?

Even though #3 has been merged, we do not have organization-level discussions nor did https://eclipse-thingweb.github.io/.eclipsefdn/ get updated. @netomi is there some time we should wait for it to happen?