git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Outreachy]

From
ASAbraham Samuel <sammymore50@gmail.com>
Date
Oct 6, 2024, 09:57 UTC
Message-ID
<CAO1n887hN81j5h12t-6xpNQAQ5uOx1wxLz48c+O4hZE-pWdY8A@mail.gmail.com>
In-Reply-To
<CAO1n887uu5qUcqLcdKfh8FBKJAQUCGqVOnAzX7WWiFEnuuMF3A@mail.gmail.com>
Hi Philip,
I have read through [1], [2] and other articles relevant to completing
a micro project and contributing to git. After going through the
microproject ideas, I have come up with two possible projects I am
interested in working on.
1. changing the style for 'cd' in the test subshell.
In this following email,
https://lore.kernel.org/git/CAPig+cQpUu2UO-+jWn1nTaDykWnxwuEitzVB7PnW2SS_b7V8Hg@mail.gmail.com/
It explains how to modernise and clean up t7001, and example of which is
* style for `cd` in subshell is:
    (
        cd foo &&
        ...
    ) &&
  not:
    (cd foo &&
        ...
    ) &&.
However, a sample outdated style can be seen in the sample file
t/t5605-clone-local.sh which I would like to work on to change those
instances to the modern accepted code style
Some examples can be seen in the file as follows.
test_expect_success 'local clone without .git suffix' '
git clone -l -s a b &&
(cd b &&
echo false >expect &&
git config --bool core.bare >actual &&
test_cmp expect actual &&
git fetch)
'
test_expect_success 'local clone with .git suffix' '
git clone -l -s a.git c &&
(cd c && git fetch)
'
test_expect_success 'bundle clone with nonexistent HEAD (match default)' '
git clone b2.bundle b2 &&
(cd b2 &&
git fetch &&
git rev-parse --verify refs/heads/main)
'
2. Use test_path_is_* functions in test scripts.
I have found three potential test files in the t/ directory
t5601-clone.sh
test_expect_success 'clone --mirror' '

git clone --mirror src mirror && test -f mirror/HEAD && test ! -f mirror/file && FETCH="$(cd mirror && git config remote.origin.fetch)" && test "+refs/*:refs/*" = "$FETCH" && MIRROR="$(cd mirror && git config --bool remote.origin.mirror)" && test "$MIRROR" = true

'

t7300-clean.sh test_expect_success 'git clean with skip-worktree .gitignore' ' git update-index --skip-worktree .gitignore && rm .gitignore && mkdir -p build docs && touch a.out src/part3.c docs/manual.txt obj.o build/lib.so && git clean && test -f Makefile && test -f README && test -f src/part1.c && test -f src/part2.c && test ! -f a.out && test ! -f src/part3.c && test -f docs/manual.txt && test -f obj.o && test -f build/lib.so && git update-index --no-skip-worktree .gitignore && git checkout .gitignore ' t7611-merge-abort.sh test_expect_success 'fails without MERGE_HEAD (completed merge)' ' git merge clean_branch && test ! -f .git/MERGE_HEAD && # Merge successfully completed post_merge_head="$(git rev-parse HEAD)" && test_must_fail git merge --abort 2>output && test_grep MERGE_HEAD output '

These tests can be refactored to use the test_path_is_file and test_path_is_missing functions.

Please kindly let me know the possibility of doing these microprojects. Thanks Abraham. On Thu, Oct 3, 2024 at 3:14 AM Abraham Samuel <sammymore50@gmail.com> wrote:

Show 29 quoted lines
>
> Hello Philip, thanks for your prompt response. As regards your
> request, I want to work on the project description 'Convert unit tests
> to use the clar testing framework'.
>
> On Wed, Oct 2, 2024 at 3:04 PM Phillip Wood <phillip.wood123@gmail.com> wrote:
> >
> > Hi Abraham
> >
> > On 02/10/2024 04:04, Abraham Samuel wrote:
> > > Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and
> > > eager to start making valuable contributions to this project. Thanks
> >
> > Happy to hear that you are interested in contributing to Git as part of
> > the Outreachy projet. To help us mentors, could you please clarify which
> > of the two approved projects you are interested in?
> >
> > Other than that I would strongly recommend reading through [1] and [2],
> > if you haven't already done so. They should give you some ideas for how
> > the Outreachy application process is designed to work in the Git project
> > and lays out the expectation of us mentors.
> >
> > Let me know in case you have any additional questions.
> >
> > Phillip
> >
> > [1]: https://git.github.io/Mentoring-Program-Guide/
> > [2]: https://git.github.io/General-Microproject-Information/
> >
Previous: Abraham SamuelNext: Patrick Steinhardt
Message 4 of 8 in “[Outreachy]”
  1. Abraham SamuelOct 2, 2024
  2. Phillip WoodOct 2, 2024
  3. Abraham SamuelOct 3, 2024
  4. Abraham SamuelOct 6, 2024
  5. Patrick SteinhardtOct 7, 2024
  6. Abraham SamuelOct 7, 2024
  7. Abraham SamuelOct 8, 2024
  8. Abraham SamuelOct 7, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.