You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bundler-related-issue.md
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,9 @@ assignees: ''
9
9
10
10
<!--
11
11
12
-
Thank you for contributing to the [rubygems](https://github.com/rubygems/rubygems) repository, and specifically to the [Bundler](https://bundler.io/) gem.
12
+
Thank you for contributing to the rubygems) repository, and specifically to the Bundler gem.
13
13
14
-
Sometimes you can find a solution to your issue by reading some documentation.
15
-
16
-
* Instructions for common Bundler uses can be found on the [Bundler documentation site](https://bundler.io/).
17
-
* Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](https://bundler.io/man/bundle.1.html) or [Bundler Command Line Reference](https://bundler.io/commands.html).
18
-
* We also have a document detailing solutions to common problems: https://github.com/rubygems/rubygems/blob/master/bundler/doc/TROUBLESHOOTING.md.
19
-
20
-
If you're still stuck, please fill in the following sections so we can process your issue as fast as possible:
14
+
Please fill in the following sections so we can process your issue as fast as possible
21
15
22
16
-->
23
17
@@ -53,7 +47,7 @@ Fill this with a list of steps maintainers can follow to reproduce your issue. N
53
47
54
48
The more complete the steps to simulate your particular environment are, the easier it will be for maintainers to reproduce your issue on their machines.
55
49
56
-
Ideally, we recommend you set up the list of steps as a [Dockerfile](https://docs.docker.com/get-started/). A Dockerfile provides a neutral environment that should give the same results, no matter where it's run.
50
+
Ideally, we recommend you set up the list of steps as a Dockerfile. A Dockerfile provides a neutral environment that should give the same results, no matter where it's run.
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
<!--
2
2
Thanks so much for the contribution!
3
3
4
-
Note that you must abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md) to contribute to this project.
5
-
6
4
To make reviewing this PR a bit easier, please fill out answers to the following questions.
7
5
-->
8
6
@@ -19,6 +17,6 @@ alternatives, explain why you end up choosing the current implementation -->
19
17
## Make sure the following tasks are checked
20
18
21
19
-[ ] Describe the problem / feature
22
-
-[ ] Write [tests](https://github.com/rubygems/rubygems/blob/master/bundler/doc/development/PULL_REQUESTS.md#tests) for features and bug fixes
20
+
-[ ] Write [tests](https://github.com/rubygems/rubygems/blob/master/doc/bundler/development/PULL_REQUESTS.md#tests) for features and bug fixes
23
21
-[ ] Write code to solve the problem
24
22
-[ ] Make sure you follow the [current code style](https://github.com/rubygems/rubygems/blob/master/doc/bundler/development/PULL_REQUESTS.md#code-formatting) and [write meaningful commit messages without tags](https://github.com/rubygems/rubygems/blob/master/doc/bundler/development/PULL_REQUESTS.md#commit-messages)
0 commit comments