Opentelemetry-specification: Do we really need "branch must be up to date" restriction?

[yurishkuro]

931 is approved, but I, as admin, cannot merge it, nor can I merge master to make it pass this check.

cc @open-telemetry/technical-committee

[Oberon00]

Duplicate of #512

[carlosalberto]

+1 on this, as it creates too much hassle (but IIRC @bogdandrutu had a reason to enable this).

[Oberon00]

@yurishkuro I updated the PR in question (I have access to that Dynatrace repository)

[yurishkuro]

The reasoning in #512 is

Because we fixed the lint check (broken for 2 months) and started to merge PRs that did not pass the lint check (based on master commit that did not include the fix). This was the only option to enforce that everyone pass the lint check.

I am not convinced it's a good reason, more a reaction to one time issue where bad commits were made due to lack of lint enforcement.

[Oberon00]

IMHO fixing the lint with quick follow-up PRs on master is easier than pinging people to update their PRs with organization-owned repos.

[carlosalberto]

Agreed that we should perhaps revert this. @bogdandrutu You ok with that? ;)

[andrewhsu]

From the issue triage mtg today, if @open-telemetry/technical-committee can either execute this requested change or close this issue.

[carlosalberto]

cc @SergeyKanzhelev

[SergeyKanzhelev]

I'm ok reverting it. It's easier to fix issue than block PR merges