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-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ If you're still stuck, please fill in the following sections so we can process y
23
23
24
24
### Describe the problem as clearly as you can
25
25
26
-
<!-- Replace this with an explanation of the problem you are having. Be as much clear and precise as you can. -->
26
+
<!-- Replace this with an explanation of your problem. Be as clear and precise as you can. -->
27
27
28
28
### Did you try upgrading rubygems & bundler?
29
29
@@ -44,7 +44,7 @@ might do the trick, and will also save us some time :)
44
44
45
45
<!--
46
46
47
-
Fill this with a list of steps maintainers can follow to reproduce your issue. Note that while you are seeing this issue in your computer, maintainers might not see the same thing on theirs. There is a number of things that could influence this:
47
+
Fill this with a list of steps maintainers can follow to reproduce your issue. Note that while you see this issue in your computer, maintainers might not see the same thing on theirs. There are many things that could influence this:
48
48
49
49
* How your ruby is setup (OS package, from source, using a version manager).
50
50
* How bundler & rubygems are configured.
@@ -53,7 +53,7 @@ Fill this with a list of steps maintainers can follow to reproduce your issue. N
53
53
54
54
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
55
56
-
Ideally, we recommend you to 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.
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.
0 commit comments