Prow config is mixing camelCase, _underscores _, and -hyphens-

[0xmichalis]

• camelCase, eg. missingLabels in the tide config
• underscores, mostly used eg. push_gateway
• hyphens, eg. branch-protection

We should probably converge to a single format and stick with it.

@fejta @stevekuznetsov @cjwagner @BenTheElder @krzyzacy

/area prow

[0xmichalis]

/shrug

[stevekuznetsov]

+1 to snake_case IMO

[BenTheElder]

/kind bug
/area bikeshed

[BenTheElder]

we should also document whatever we move to somewhere or have a config linter to prevent regressions.

[cjwagner]

I vote hyphens, but I don't care much as long as we are consistent.

[fejta]

pronounSubject_I verbPredicate_Think pronounSubject_We verbAuxilliary_Should verbPredicate_Use adjective_Hungarian nounDirect_Notation

[fejta]

We should make label_sync randomly assign a new color to the area/bikeshed label whenever the tool runs

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[stevekuznetsov]

/remove-lifecycle stale

If we want to look like k8s we should go with camelCase. Generically, can we write a serializer that loads either from field_name if present or fieldName if not? then we can do this migration slowly.

[BenTheElder]

We can add a new type embedding the real type temporarily that exposes the alternate field and then fixup that type into the real type.

+1 for going k8s style with camelCase for consistency.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[idealhack]

/remove-lifecycle rotten

[spiffxp]

/lifecycle frozen
/remove-kind bug
/kind cleanup
/milestone 2019-goals

Consistency helps discoverability and adoption

[spiffxp]

/remove-lifecycle frozen
all the inconsistencies remain

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.