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

[GSoC][Newbie] Test Script Enhancements

From
Rhythm Narula <rhythm.narula26@gmail.com>
Date
Jan 5, 2025, 09:39 UTC
Message-ID
<CAKz1=ZOY7GziF9DNTLXv=G+OX8_vAbvOYS4L2s-D2C3kpr-zOg@mail.gmail.com>

Hi Everyone, My name is Rhythm Narula and I am currently working as a Software Engineer. I had the privilege of participating in GSoC 2023 with Pitivi, GNOME, where I completed a project on generating closing credit clips. LinkedIn - https://www.linkedin.com/in/rhythm-narula-34b652191/

As someone who uses Git daily for version control and collaboration, I have developed a strong interest in understanding its internals and contributing to its improvement, allowing me to impact millions of developers worldwide.

I understand that GSoC 2025 mini project ideas have not yet been released, however, I have been exploring 2024 mini project ideas and noticed a few areas where improvements might still be possible. I have outlined these below and world appreciate your feedback on whether these are accurate and worth pursuing:

1. Avoid suppressing git’s exit code in test scripts
a.  diff --git a/t/t5801-remote-helpers.sh b/t/t5801-remote-helpers.sh
index d21877150e..3433fcfc44 100755
--- a/t/t5801-remote-helpers.sh
+++ b/t/t5801-remote-helpers.sh
@@ -271,7 +271,7 @@ test_expect_success 'push update refs failure' '

 clean_mark () {
        cut -f 2 -d ' ' "$1" |
-       git cat-file --batch-check |
+       git cat-file --batch-check >actual &&
        grep commit |
        sort >$(basename "$1")
 }

2. Modernize a test script
Is there anyone working on t/t5801-remote-helpers.sh? Can I take this up?

Regards,
Rhythm
Next: Eric Sunshine
Message 1 of 2 in “[GSoC][Newbie] Test Script Enhancements”
  1. Rhythm NarulaJan 5, 2025
  2. Eric SunshineJan 5, 2025

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.