-
Notifications
You must be signed in to change notification settings - Fork 33
fix(footer) : Dynamically update copyright year #33
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
Conversation
There was a problem hiding this 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
|
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! |
Achanandhi-M
left a comment
There was a problem hiding this 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?
|
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. |
|
“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?” |
Signed-off-by: Achanandhi-M <[email protected]> Signed-off-by: Gourav <[email protected]>
Signed-off-by: Gourav <[email protected]>
…gram #3038) Signed-off-by: Gourav <[email protected]>
|
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 |
|
recheck |
|
I have read the CLA Document and I hereby sign the CLA |
|
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? |
|
recheck |
|
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! 💛 |
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
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)
Checklist:
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