Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback footer - Final review #119

Closed
5 tasks done
Kevils opened this issue Feb 17, 2025 · 25 comments · Fixed by #132
Closed
5 tasks done

Feedback footer - Final review #119

Kevils opened this issue Feb 17, 2025 · 25 comments · Fixed by #132
Assignees
Labels
Good first issue Good for newcomers OD Build Issue reserved for the OD Build Open for contribution An issue that is available for an Only Dust contribution

Comments

@Kevils
Copy link
Collaborator

Kevils commented Feb 17, 2025

Description 📹

Issues :

Your task will be to check that all the issues have been correctly developed, that the components are properly arranged, and that everything matches exactly as on issues

Proposed Actions 🛠️

Here’s a checklist of actions to follow for resolving this issue:

  1. Fork and Create Branch:
    Fork the repository and create a new branch using the issue number:

    git checkout -b fix-[issue-number]
  2. Implement Changes:
    [Insert Code snippet if needed with a mardown todo list]

  3. Run Tests and Commit Changes:
    Make sure your changes don't break existing functionality and commit with a clear message:

    git commit -m "Fix: [Short description of the fix]"

Required 📋

To keep our workflow smooth, please make sure you follow these guidelines:

  • Assignment: Don't create a pull request if you weren’t assigned to this issue.
  • Timeframe: Complete the task within 3 business days.
  • Closing the Issue: In your PR description, close the issue by writing Close #[issue_id].
  • Review Process:
    • Once you've submitted your PR, change the label to "ready for review".
    • If changes are requested, address them and then update the label back to "ready for review" once done.
  • Testing: Test your PR locally before pushing, and verify that tests and build are working after pushing.

Thank you for your contribution 🙏

⚠️ WARNING: Failure to follow the requirements above may result in being added to the OnlyDust blacklist, affecting your ability to receive future rewards.

@Kevils Kevils added Good first issue Good for newcomers Open for contribution An issue that is available for an Only Dust contribution labels Feb 17, 2025
@Thosine-01
Copy link

Can I take up this issue

@sublime247
Copy link

sublime247 commented Feb 17, 2025

Hi @Kevils , I’m Bashir, a software engineer specializing in front-end and mobile development. 🚀
I have vast coding experience building with TypeScript, JavaScript, and Rust. ⚡️
I’ve contributed to a couple of projects on Onlydust successfully. 🔥

I’ll get this task solved in little time.

Kindly assign this task to me.
ETA:
I can complete this task within 5 hours Max. ⏳
Looking forward to contributing! 🚀


Thanks!

@Adebisi1234
Copy link

Adebisi1234 commented Feb 17, 2025

Hi, I'd like to take this issue

I'm a skilled full stack developer

Here's my portfolio: https://tobiloba.me/portfolio

And ETA: 4hrs

@tali-creator
Copy link

I have worked as a project manager and also a developer on same project, so I believe I can handle this task perfectly if given the opportunity to

Thank you

@Cedarich
Copy link

Please can i work on this

@legend4tech
Copy link

Is it okay if I tackle this?

@rajendrakrshaw
Copy link

Subject: Application for Issue Resolution - Starknet ID Repository

Dear Maintainers,

I hope this message finds you well. I am writing to express my interest in contributing to the resolution of the following issues in the app.starknet.id repository:

Plan of Action

To ensure that the issues are correctly addressed, I will follow these steps:

  1. Fork and Create a Branch:

    • I will fork the repository and create a dedicated branch for each issue.
    • Example:
      git checkout -b fix-1018
  2. Implement Changes:

    • Review the issue description and analyze the expected outcome.
    • Ensure that components are properly arranged and match the required specifications.
    • Make necessary modifications to resolve the issues while maintaining code integrity.
  3. Testing and Validation:

    • Perform local testing to confirm that the implemented changes work as expected.
    • Ensure that all tests pass and that the build is stable.
  4. Commit and Push Changes:

    • Use clear and descriptive commit messages:
      git commit -m "Fix: Resolves issue lfglabs-dev/starknet.id#120 by adjusting component layout"
    • Push the changes to my fork and open a Pull Request with a reference to the issue.
  5. Follow Contribution Guidelines:

    • Verify that I am assigned to the issue before opening a PR.
    • Complete the task within the specified timeframe of three business days.
    • Mention Close #[issue_id] in the PR description to link and close the issue.
    • Label the PR as "ready for review" once submitted.
    • Address requested changes promptly and update the label accordingly.

Why I Am a Good Fit

I have experience in frontend and backend development, with a strong focus on ensuring that UI components are well-structured and functional. My attention to detail and adherence to project guidelines will help me efficiently resolve these issues while maintaining code quality.

I am eager to contribute to this project and look forward to your approval to proceed with these tasks.

Best Regards,
Rajendra Kumar Shaw

@pheobeayo
Copy link

Is this issue still available?
Can I give this a shot

@Brain-codes
Copy link

I'm Adenuga Adewumi Efe, a JavaScript, React, and TypeScript developer with 6+ years of experience delivering high-quality, responsive, and scalable web applications.

My Plan:
✅ Review and implement necessary fixes for the wager summary components using React and TypeScript.
✅ Ensure accurate UI rendering based on Figma design specifications.
✅ Optimize component structure, state management, and responsiveness.
✅ Conduct thorough testing and validation before submission.

ETA:
I can complete this task within 2 to 3 days.

Looking forward to contributing! 🚀

@kellymusk-hash
Copy link

Could I grab this task?

@Richardudeh4
Copy link

I’d like to work on this.

@lynaDev2
Copy link

Could I take a shot at this?

@viktrified
Copy link

Hello! My name is Victory, I'm a frontend dev and I'm very conversant with git and projects workflows. If given this issue I'll test and crosscheck the project's footer and make sure its ready. I'll complete this in 24hrs

@Viktohblake
Copy link

Could I grab this task?

@wendycooper23
Copy link

I’d like to help with this.

@iGEORGE17
Copy link

May I pick this up?high priority

@HyzeahAchungha
Copy link

Let me handle this issue!

@Elozzy
Copy link

Elozzy commented Feb 20, 2025

Could I try solving this?

@marezgui
Copy link

I’d like to resolve this.

@OgbuGideon
Copy link

Hi, my name is Gideon and i am a front-end developer with experience solving problems using front-end technologies such as typescript, javascript and react. This is my first time contributing on this platform. I have gone through the projects and i am particularly interested in contributing to this. I am very confident that i can deliver this within the specified time.

ETA <= 24hrs

@kaydeemoney
Copy link

Could I take over this issue?

@alexohre
Copy link
Contributor

Hi, I'm Alex Ohre, a software developer with experience in Typescript, Javascript, Ruby, Tailwinds, Bootstrap, and a few others. I'm excited to contribute to this project and help resolve the outstanding issues. (first-time contributor 🫣 )

  • Using a responsive design approach to adjust the footer layout based on screen size.
  • Implementing a flexible grid system to ensure the footer elements adapt to different screen sizes.

ETA: 12hrs

@Kevils Kevils transferred this issue from lfglabs-dev/app.starknet.id Feb 21, 2025
@aritrachatterjee7
Copy link
Contributor

@Kevils can i take up this issue?

@OWK50GA
Copy link

OWK50GA commented Feb 21, 2025

Hi, I'll love to work on this

@aritrachatterjee7
Copy link
Contributor

aritrachatterjee7 commented Feb 21, 2025

@Marchand-Nicolas @Kevils
Please mark this PR as "Ready for Review". All changes are implemented and tested locally. 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good first issue Good for newcomers OD Build Issue reserved for the OD Build Open for contribution An issue that is available for an Only Dust contribution
Projects
None yet