hey, thanks for taking so much time with this.

i'm a bit confused about git and i want to be a good github citizen, so
maybe you can give me some guidance...

i've read a bit about pull requests and rebasing, but i'm confused because
of the loud warnings not to rebase commits that have appeared on a remote
already.

git won't let me push my branch to my github fork unless i first do a pull.
but the pull gives me all sorts of commits from the upstream.

should i just push to my branch, and update the pull request, even though
it'll mean my tiny addition has several commits to clutter your history? or
should i rebase in a way that would roll up all of the unrelated commits,
or discard them, or something?

everyone on stackoverflow seems to be confused about how to properly do
this...

thanks!

-Ben

--------------------
Ben Wheeler
mobile 917.254.1578


On Wed, Jan 8, 2014 at 3:40 PM, Erik Michaels-Ober <notifications@github.com
> wrote:

> In examples/Search.md:
>
> > +
> > +See the [Configuration][] example for info about keys/tokens/secrets.
> > +
> > +[Configuration]: https://github.com/sferik/twitter/blob/master/examples/Configuration.md
> > +
> > +```ruby
> > +require 'twitter'
> > +
> > +client = Twitter::REST::Client.new do |config
> > +  config.consumer_key = "YOUR_CONSUMER_KEY"
> > +  config.consumer_secret = "YOUR_CONSUMER_SECRET"
> > +  config.access_token = "YOUR_ACCESS_TOKEN"
> > +  config.access_token_secret = "YOUR_ACCESS_SECRET"
> > +end
> > +
> > +client.search("#helloworld", :count => 10).each do |tweet|
>
> Using the same search is fine with me.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/sferik/twitter/pull/505/files#r8738199>
> .
>