I just want to clarify that if someone finds an error in the docs or a bug,
it's perfectly fine to just send a bug report:
* Inside Racket: Go to the menu > About > Submit Bug Report ...
* In Github: Submit an "Issue"
Please include enough information to reproduce the bug. For example for a
I agree with Greg that such a feature would be neat - so it's great that
Ben and Kieran are on it already. (Thanks!)
The CONTRIBUTING.md is a good idea (and I David's version). The 'Edit on
Github' button would solve the first stumbling block I hit, while the
contribution.md file helps later in
On 3/8/19, David Storrs wrote:
> On Fri, Mar 8, 2019 at 3:13 PM Greg Hendershott
> wrote:
>
>> I have a dumb question. Why can't doc pages have links whose label is
>> something like "Want to improve the docs?", and the URL goes directly
>> to the appropriate .scrbl file on GitHub?
>>
>
> I
On Fri, Mar 8, 2019 at 3:13 PM Greg Hendershott
wrote:
> I have a dumb question. Why can't doc pages have links whose label is
> something like "Want to improve the docs?", and the URL goes directly
> to the appropriate .scrbl file on GitHub?
>
I asked about this a year or so ago and the
Thank you for that writeup, Marc. I've wanted to offer doc changes several
times but never had the spoons to figure out how.
Matthew, I think you're absolutely right: putting this in a CONTRIBUTING
file would be great. I've created one and submitted a pull request. :>
On Fri, Mar 8, 2019 at
I have a dumb question. Why can't doc pages have links whose label is
something like "Want to improve the docs?", and the URL goes directly
to the appropriate .scrbl file on GitHub?
- A .scrbl file knows its own syntax source file path.
- defmodule forms know how to make links to the package
Perhaps this would be good material for a CONTRIBUTING.md at the top level of
the repo, where it would be more likely to be found by future contributors.
GitHub will automatically show a link to the file at arguably appropriate
times. [1]
[1]
Let me (ab)use this thread to add some more details on how to submit pull
requests (PR) on GitHub to racket using the GitHub web interface for other
noobs - which includes myself in another month or two. Ideally I would
write this up elsewhere to help with onboarding, but that won't happen
soon,
Ergh, of course I forgot to do that part. Thanks for catching that.
On Thu, Mar 7, 2019 at 1:59 PM Paulo Matos wrote:
>
>
> On 07/03/2019 13:40, Marc Kaufmann wrote:
> > Thanks Paulo, this is way better than the workflow I used the only other
> > time I made a PR. The only thing I had to do was
On 07/03/2019 13:40, Marc Kaufmann wrote:
> Thanks Paulo, this is way better than the workflow I used the only other
> time I made a PR. The only thing I had to do was choose a branch to
> commit to: I chose 'master', mostly because I have no clue what else I
> would have chosen. What is the
On 07/03/2019 13:40, Marc Kaufmann wrote:
> Thanks Paulo, this is way better than the workflow I used the only other
> time I made a PR. The only thing I had to do was choose a branch to
> commit to: I chose 'master', mostly because I have no clue what else I
> would have chosen. What is the
Thanks Paulo, this is way better than the workflow I used the only other
time I made a PR. The only thing I had to do was choose a branch to commit
to: I chose 'master', mostly because I have no clue what else I would have
chosen. What is the default to contribute to?
It was in scribblings by the
On 07/03/2019 11:55, Marc Kaufmann wrote:
> Hi,
>
> I just came across a typo in the documentation and was about to move on
> simply because I couldn't be bothered to figure out how/where to change
> it. I couldn't find the docs in the github repo (I searched for doc, and
> looked under
13 matches
Mail list logo
