Skip to content

Conversation

@Gouravjaat07
Copy link

Pull Request Template

Description

Fixes issue #3038 by updating the copyright year in the footer of the Writer’s Program website from 2023 → 2025. The change ensures the correct year is displayed consistently across all pages.

Motivation: Keep website information up-to-date.

Dependencies: None.

Fixes # (3038)

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • Run the project locally using start index.html.

  • Verified the footer displays 2025 on all pages.

Additional Context (Please include any Screenshots/gifs if relevant)

Screenshot 2025-09-24 073317

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings
  • I have tagged the reviewers in a comment below incase my pull request is ready for a review
  • I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

Thanks for opening this pull request! If the tests fail, please feel free to reach out to us by leaving a comment down below and we will be happy to take a look

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you and congratulations 🎉 for opening your very first pull request in writers-program

@Gouravjaat07
Copy link
Author

Hi sir @Achanandhi-M , I’ve submitted PR #33 fixing issue #3038. Could you please review it when you get time? I’m new to contributing and would love feedback. Thanks!

Copy link
Member

@Achanandhi-M Achanandhi-M left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Gouravjaat07 currently the pipeline is failing can you please check it and fix the issue?

@Gouravjaat07
Copy link
Author

Thanks for pointing it out @Achanandhi-M . I’ll check the pipeline logs, fix the DCO and CLI test failures, and update the PR accordingly.

@Gouravjaat07
Copy link
Author

“Hey @Achanandhi-M , the CLA Assistant check is failing but I don’t see any Sign CLA button. Could you please re-trigger the CLA bot?”

@Achanandhi-M
Copy link
Member

Hey @Gouravjaat07 you have to just comment "recheck" or "I have read the CLA Document and I hereby sign the CLA" it will automatically pass

@Gouravjaat07
Copy link
Author

recheck

@Gouravjaat07
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@Gouravjaat07
Copy link
Author

Hey @Achanandhi-M , I’ve tried commenting recheck and the CLA sign phrase, but the check is still failing. Could you please re-trigger the CLA Assistant from your side?

@Gouravjaat07
Copy link
Author

recheck

@Achanandhi-M
Copy link
Member

Hey @Gouravjaat07 , thank you so much for raising this PR! 🙌 We’ve already merged similar changes from another contributor, so we’ll be closing this one.

We really appreciate your effort and would love for you to pick a new good first issue — your contributions are always welcome! 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants