Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gist for Active Record issues [ci skip] #9775

Closed
wants to merge 1 commit into from
Closed

gist for Active Record issues [ci skip] #9775

wants to merge 1 commit into from

Conversation

neerajdotname
Copy link

In order to make it easier to verify Active Record issues
bug authors are encouraged to provide gist based on provided
templates

@neerajdotname
Copy link
Author

@fxn Please take a look.

@senny
Copy link
Member

senny commented Mar 18, 2013

This is a great idea! I spent many hours trying to reproduce AR issues, and many times it resulted in an incomplete bug report. This would safe a ton of time and help to check what versions are affected by the bug.

/cc @carlosantoniodasilva @rafaelfranca @steveklabnik

@fxn
Copy link
Member

fxn commented Mar 18, 2013

Looks good.

If the templates are too big for being inlined (they probably are) I believe we should store them in the repo and link to GitHub.

@rafaelfranca
Copy link
Member

👍 for what @fxn said.

@steveklabnik
Copy link
Member

You are amazing. 👍

@@ -30,6 +30,19 @@ At the minimum, your issue report needs a title and descriptive text. But that's

Then, don't get your hopes up! Unless you have a "Code Red, Mission Critical, the World is Coming to an End" kind of bug, you're creating this issue report in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the issue report will automatically see any activity or that others will jump to fix it. Creating an issue like this is mostly to help yourself start on the path of fixing the problem and for others to confirm it with an "I'm having this problem too" comment.

### Create a gist for Active Record Issues

If you filing Active Record bug then in order to make it easier to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*are

@neerajdotname
Copy link
Author

@vipulnsward @stevenharman thanks and fixed .

* If you are using master version of Rails then create a gist [like
this](https://gist.github.com/neerajdotname/5187194). Note that in this
case both Gemfile and test file are needed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gemfile

In order to make it easier to verify Active Record issues
bug authors are encouraged to provide gist based on provided
templates
@neerajdotname
Copy link
Author

@fxn Can you take it from here? I think it's better to hand over it to you rather than asking questions like where to store the templates etc. Thank you.

@fxn
Copy link
Member

fxn commented Mar 18, 2013

@neerajdotname sure, thanks!

fxn added a commit that referenced this pull request Apr 1, 2013
@fxn
Copy link
Member

fxn commented Apr 1, 2013

I gave it another iteration, the gist for reports against the master branch is also self-contained.

Thanks for this proposal, it is a great idea.

@fxn fxn closed this Apr 1, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants