eiffel-community / .github Goto Github PK

Description

The logo on the organization readme does not work as can be seen on https://github.com/eiffel-community

Motivation

Bad experience for the visitor

Exemplification

N/A

Benefits

Broken images are not a good sign

Possible Drawbacks

None

Description

The directory-style pull request template introduced in #8 apparently doesn't work. Such named templates only work when accessed with a custom URL. The default template is still .github/PULL_REQUEST_TEMPLATE.md, a file that didn't exist as of said commit so we currently end up without a template.

Motivation

We want to have a PR template and right now it doesn't work.

Exemplification

N/A

Benefits

Working PR template.

Possible Drawbacks

None.

Description

There is currently a Copyright message at the top of the raw CONTRIBUTING.md file.
Should it be there?

Motivation

Just a question :)

Exemplification

Benefits

Possible Drawbacks

Description

Nowadays a repository can have multiple templates for issues and PRs, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates. While we currently don't have more than one template for either type of entity this could be useful in the future. In fact, it already is in the community repository; see eiffel-community/community#101.

Motivation

Using the new style of templates in this repository would enable a few more features apart from the ability to have multiple templates, and for other eiffel-community repositories that add their own templates it might be easier to understand how they interact with the ones in this repository if they use the same style.

Exemplification

It's totally conceivable that we'll want to have separate issue templates for bug reports and feature requests, and that's not possible with the legacy template style.

Benefits

More features that make our repositories friendlier and more convenient to work with.

Possible Drawbacks

None.