Frankly this is properly a GitHub FAQ question. Nobody with github
experience will learn anything from this. And it's certainly not Scala IDE
specific. A Readme is mandatory reading and a project-specific reference
document (with mostly pointers to INSTALL, contact and mailing list info
and authorship info), and for that reason, I hate the cluttered ones. If
ours were to educate people on GitHub etiquette, it would also probably
include an email etiquette FAQ, maven and eclipse manuals, and whatnot ...
-- 
FG

-- 
FG
On Mar 21, 2013 9:26 AM, "Mirco Dotta" <notifications@github.com> wrote:

> In src/sphinx/dev/workflow/workflow.rst:
>
> > +.. note::
> > +
> > +       If your pull request required further changes as a result
> > +       of a failed build, please add more commits but do not
> > +       `force push
> > +       <https://help.github.com/articles/dealing-with-non-fast-forward-errors>`_
> > +       against the branch your pull request is issued from. From
> > +       the moment your pull request is issued, you can consider
> > +       it public and shared by reviewers (and the build kitteh),
> > +       something that does not play well with trying to rewrite
> > +       history. If it is absolutely necessary to rewrite what you
> > +       submitted as a pull request, please consider closing your
> > +       pull request and re-opening another. You can trigger
> > +       another build from the kitteh (e.g. after making a few
> > +       additions) by commenting against your pull request with
> > +       the string ``PLS REBUILD ALL``.
> >
>
> I'm thinking this should be merged (as it makes sense) in
> https://github.com/scala-ide/scala-ide/blob/master/README.md and then we
> should just have a link to the latter.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/scala-ide/docs/pull/51/files#r3466453>
> .
>