Re: [PATCH v1 1/1] ci: facilitate dev to mimic a CI environment
- From
- Stavros Ntentos <stdedos@gmail.com>
- Date
- Mar 27, 2021, 09:08 UTC
- Message-ID
- <20210327090813.7847-1-133706+stdedos@users.noreply.github.com>
- In-Reply-To
- <5196a86c-1153-8998-a8cb-c8bd20687150@gmail.com>
Show 9 quoted lines
> > diff --git a/Documentation/howto/setup-local-dev-environment-docker.sh b/Documentation/howto/setup-local-dev-environment-docker.sh > > new file mode 100644 > > index 0000000000..265602ea55 > > --- /dev/null > > +++ b/Documentation/howto/setup-local-dev-environment-docker.sh > > @@ -0,0 +1,43 @@ > > +#!/bin/false > Wait, why did you make this documentation /bin/false script? I think > it is better to be in Asciidoc format (.txt)
My full intention was to actually _create_ a script that would put a wanna-be developer (me) from (a) looking at my terminal inside git/, to (b) have a ci-like environment, inside an abstraction layer (docker) with linked sources (i.e. the "${PWD}:/usr/src/git" part).
However, the way sources and docker invocation are defined, I find it hard to create "the script". Also because (again) my docker knowledge is limited.
I want future nitpick-fixers (hopefully with more docker experience), to look at this script with such agenda in mind - and not to "just" document their findings alongside mine.
`#!/bin/false` is simply my way of saying "it's not ready to be run yet", and I used `.sh` to get formatting / syntax highlighting cheaper than running a fully-fledged .md file.
If you still insist it's no good as a ".sh", my intention would be to make it .md (to get some formatting in it).