# [Outreachy]Microproject: modernize path checks in t1410-reflog.sh

3 messages from 2025-10-04 to 2025-10-05. Participants: Vedansh singh, Usman Akinyemi.
Thread: https://gitlist.dev/t/64247

## Vedansh singh, 2025-10-04 18:08

Subject: [Outreachy]Microproject: modernize path checks in t1410-reflog.sh
Message-ID: <CAMWvevL03vRzX35tiRCkoU6CKucKim+GfacEVuN6wwm9r+1a6Q@mail.gmail.com>
URL: https://gitlist.dev/e/CAMWvevL03vRzX35tiRCkoU6CKucKim%2BGfacEVuN6wwm9r%2B1a6Q%40mail.gmail.com

```
Hello,

I'm Vedansh and I'm interested in contributing to Git through Outreachy 2025.

I have successfully built Git from source on Ubuntu (via WSL2) and run
the test suite. All tests pass.

For my microproject, I'd like to modernize the path checking in
t/t1410-reflog.sh by replacing 'test -f' with test_path_is_file in
lines 133-136 (in the 'rewind' test).

I found 4 instances that are assertions (part of && chains):
- test -f C
- test -f A/B/E
- ! test -f F
- ! test -f A/G

I've verified these are test assertions, not flow control statements,
and the test currently passes on my system.

Is this appropriate for a microproject?

Thanks,
Vedansh

```

## Usman Akinyemi, 2025-10-05 09:41

Subject: Re: [Outreachy]Microproject: modernize path checks in t1410-reflog.sh
Message-ID: <CAPSxiM-veMq2TRJwzbRPpewrpCPYdieTjs3uR2L4e3ORQDsWgg@mail.gmail.com>
URL: https://gitlist.dev/e/CAPSxiM-veMq2TRJwzbRPpewrpCPYdieTjs3uR2L4e3ORQDsWgg%40mail.gmail.com
In-Reply-To: <CAMWvevL03vRzX35tiRCkoU6CKucKim+GfacEVuN6wwm9r+1a6Q@mail.gmail.com>

```
On Sat, Oct 4, 2025 at 11:39 PM Vedansh singh <vedh2o2@gmail.com> wrote:
>
> Hello,
>
Hello Vedansh,
> I'm Vedansh and I'm interested in contributing to Git through Outreachy 2025.
>
> I have successfully built Git from source on Ubuntu (via WSL2) and run
> the test suite. All tests pass.
Good.
>
> For my microproject, I'd like to modernize the path checking in
> t/t1410-reflog.sh by replacing 'test -f' with test_path_is_file in
> lines 133-136 (in the 'rewind' test).
>
> I found 4 instances that are assertions (part of && chains):
> - test -f C
> - test -f A/B/E
> - ! test -f F
> - ! test -f A/G
>
> I've verified these are test assertions, not flow control statements,
> and the test currently passes on my system.
Firstly, you do not need to take permission before sending patches to
the GIt community.

The main point of micro project is to get you familiar with the Git workflow.
>
> Is this appropriate for a microproject?

This is a good micro project for both GSoC and Outreach but, the
Outreachy contribution stage
has not started yet,  so it might not be considered as your
microproject for Outreachy.

I will advise you to send the patch to get you familiar with the Git
contribution workflow. The Outreachy contribution
hopefully is starting soon and you can send another patch for that.

Thanks.
Usman.

```

## Vedansh singh, 2025-10-05 10:38

Subject: Re: [Outreachy]Microproject: modernize path checks in t1410-reflog.sh
Message-ID: <CAMWvevLjSiL=9kHzke8oWBSfXycmz7hyHbjaiZza+x-DfoVWNA@mail.gmail.com>
URL: https://gitlist.dev/e/CAMWvevLjSiL%3D9kHzke8oWBSfXycmz7hyHbjaiZza%2Bx-DfoVWNA%40mail.gmail.com
In-Reply-To: <CAPSxiM-veMq2TRJwzbRPpewrpCPYdieTjs3uR2L4e3ORQDsWgg@mail.gmail.com>

```
> I have successfully built Git from source on Ubuntu (via WSL2) and run
> the test suite. All tests pass.
>Good.
Thanks

> Firstly, you do not need to take permission before sending patches to the GIt community.
I tried to send patch using GitGitGadget but got Error: User Imvedansh
is not yet permitted to use GitGitGadget

>The main point of micro project is to get you familiar with the Git workflow.
Yes, couldn't agree more.

> This is a good micro project for both GSoC and Outreach but, the
> Outreachy contribution stage
> has not started yet,  so it might not be considered as your
> microproject for Outreachy.
I wanted to start a little early and get a better hold on the
contribution workflow. I’ll try to pick up more issues that need work,
which will help me integrate better with the community.

>I will advise you to send the patch to get you familiar with the Git
> contribution workflow. The Outreachy contribution
> hopefully is starting soon and you can send another patch for that.
Thank you for the guidance! Yes, I’ll go ahead with the patch now so I
can get familiar with the Git contribution workflow. Once the
Outreachy contribution period begins, I’ll pick another issue and
prepare a fresh patch for that.

Regard,
Vedansh

```