Open piotmag769 opened 3 months ago
I am applying to this issue via OnlyDust platform.
I'm Joseph a blockchain developer with over four years in blockchain and backend development, I’ve worked across different ecosystems, handling everything from smart contract design to on-chain interactions and protocol integration. I focus on building secure, scalable, and reliable blockchain applications, managing both on-chain and off-chain infrastructure.
Begin by studying the codebase to ensure design consistency, then proceed to work on the task.
I am applying to this issue via OnlyDust platform.
Hello I'm a front-end and a blockchain developer. I will love to work on this
I am applying to this issue via OnlyDust platform.
Hello @piotmag769, I would love to do this
in starknet-foundry/crates/forge/src/init.rs
update
fn extend_gitignore(path: &Path) -> Result<()> {
let mut file = OpenOptions::new()
.append(true)
.open(path.join(".gitignore"))?;
writeln!(file, ".snfoundry_cache/")?;
Ok(())
}
add new files|directories to be ignored
I am applying to this issue via OnlyDust platform.
Rust experience and a regular Foundry user for Starknet smart contract testing. Regular "Cairo Book" and "Starknet By Examle" contributor. Creator and maintainer of Cairo learning track on Exercism. As a regular Foundry user, I'm very interested in making it as efficient and as clean as possible.
I would update the extend_gitignore
function to append the files from the description.
https://github.com/foundry-rs/starknet-foundry/blob/12d2bd4b852d576f545d3876b6f49349db2f122a/crates/forge/src/init.rs#L140
Update the relevant test to assert these new files were actually created; this would also require validating that .gitignore
was actually created in the first place.
https://github.com/foundry-rs/starknet-foundry/blob/12d2bd4b852d576f545d3876b6f49349db2f122a/crates/forge/tests/e2e/running.rs#L727
I am applying to this issue via OnlyDust platform.
I have a strong background in full-stack and blockchain development, including experience with Git and managing project setups. I’ve worked with tools that create project files and automate configurations, which helped me understand how .gitignore files prevent unwanted files from being added to version control.
I will review the snforge init code to see how the .gitignore file is created and which files are excluded. I will modify the code to add snfoundry_trace, .snfoundry_cache, .snfoundry_versioned_programs, and coverage. After these changes, I’ll set up tests to ensure the updated .gitignore file is created correctly when running snforge init
I am applying to this issue via OnlyDust platform.
Hello again, my name is Deon,I am a Full-Stack web3 developer passionate about building with Rust. I have had prior experience building web3 applications/smart contracts with rust as well as creating high-performance backends.
I have a solid understanding of both backend development and data management. As an open source contributor to numerous projects, I’m committed to writing clean, maintainable code.
Firstly, I'll begin by reviewing the snforge codebase, focusing on the init functionality to determine where the .gitignore file is generated and modified.
I'll update the relevant code to include the specified paths (snfoundry_trace, .snfoundry_cache, .snfoundry_versioned_programs, and coverage) in the generated .gitignore file.
Once I'm done with that I'll create end-to-end tests to verify that running snforge init
Finally I'll ensure that the modified .gitignore behaves as expected and correctly omits the specified files from version control.
I believe using these above steps will enable me to enhance the snforge initialization process, preventing accidental inclusion of specific files and improving project organization.
Once again, I’m ecstatic about the opportunity of contributing to the Foundry project and can’t wait to get started, Do have a great day.
I am applying to this issue via OnlyDust platform.
I’m a Rust developer with experience in managing project setups and ensuring smooth version control workflows. I’ve worked on projects where improving .gitignore configurations to avoid unnecessary file commits was crucial. My experience with Rust and familiarity with git make me a good fit for this issue.
To ensure that the .gitignore
file created by snforge init
includes the necessary files, I will:
snforge init
code that generates the .gitignore
file.snfoundry_trace
.snfoundry_cache
.snfoundry_versioned_programs
coverage
.gitignore
file is automatically generated when initializing a new project with snforge init <project>
..gitignore
file contains the correct entries after snforge init
is called.I would love the opportunity to work on this issue and enhance the snforge init
setup.
I am applying to this issue via OnlyDust platform.
I’m Juan Diego, a software engineer currently working on ByteBeasts, an on-chain RPG game, and a member of the Dojo Coding community. I have strong experience with Rust, which I’ve been using extensively, and I’m also learning Cairo. I’ve contributed to various open-source projects, including work on full-stack development and blockchain solutions. I’m comfortable with project setup and automation tasks, especially managing project structures and improving workflows like .gitignore
configurations. I’m confident that my experience will allow me to contribute effectively to this task.
Review the code: I’ll begin by reviewing the snforge init functionality, especially focusing on how the .gitignore
file is currently generated and updated.
Update the .gitignore entries: I will modify the relevant part of the code to ensure the following files and directories are automatically included in the .gitignore
:
snfoundry_trace
.snfoundry_cache
.snfoundry_versioned_programs
coverage
Testing: I will create end-to-end (e2e) tests to verify that running snforge init <project>
successfully generates a .gitignore
file containing the correct entries.
Final checks: After ensuring the updated .gitignore
is generated, I’ll verify that no unintended files are included in version control and that everything works as expected.
ETA: 2-3 days
I am applying to this issue via OnlyDust platform.
Hello, can I be assigned to work on this issue?
I'm a software developer with over 6 years experience
ETA: One day
I am applying to this issue via OnlyDust platform.
Hello, can I be assigned to work on this issue?
I'm a software developer with over 4 years experience
Here's my OnlyDust profile https://app.onlydust.com/u/raizo07
ETA: One day
Hi @Akshola00 , hope everything's going well. Just wanted to touch base and ask if you have any updates on this? thanks
Hi @THenry14 Finished adding specific directories and now doing end to end testing
Which components does the task require to be changed? (think hard pls)
snforge
Description
When calling
snforge init <project>
there is a.gitignore
file created, that states what files should be omitted by the vcs. It is, however, not complete as it omits a few files that snforge is able to create during its runs, which may result in accidental inclusion of this files by git.We should modify the
snforge init
code, so it includes these files in the.gitignore
file:snfoundry_trace
.snfoundry_cache
.snfoundry_versioned_programs
coverage
Proposed steps:
Definition of done:
snforge init <project>
creates a.gitignore
file that includes paths specified in this issue