From bab81e9e7f531b9ee560e62caff59ac265ea0869 Mon Sep 17 00:00:00 2001 From: NightFlax <71522320+Nightflax@users.noreply.github.com> Date: Fri, 22 Aug 2025 08:11:57 -0600 Subject: [PATCH 1/4] Update README.md Adding required statements from the lab. --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index b103466139..884d4515d6 100644 --- a/README.md +++ b/README.md @@ -14,3 +14,23 @@ Output ``` _© 2022 XYZ, Inc._ + +Please consider the below factors while contributing + +Code Style: +Maintain a consistent code style for readability. + +Documentation: +Ensure well-documented code for effective collaboration. + +Testing: +Thoroughly test your changes before submitting a pull request. + +Issue Tracker: +Check the Issue Tracker for tasks. + +Code Review: +All contributions undergo a code review process. + +Licensing: +Contributions are licensed. From 54450379c5317c65f08dbe69c4039c5b40a83324 Mon Sep 17 00:00:00 2001 From: NightFlax <71522320+Nightflax@users.noreply.github.com> Date: Fri, 22 Aug 2025 08:15:36 -0600 Subject: [PATCH 2/4] Update CONTRIBUTING.md Extended contribution information --- CONTRIBUTING.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e8046b81b2..3923046826 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1 +1,21 @@ - All contributions, bug reports, bug fixes, documentation improvements, enhancements, and ideas are welcome. +Contribution guidelines +Welcome Contributors! + +Thank you for considering contributing to this repository. This document outlines the guidelines for contributing to the development of the Introduction to Git and GitHub repository. + +Code style +Please follow the coding style and conventions used in the existing codebase. This helps maintain consistency across the project. + +Documentation +Ensure that your contributions are well-documented. Include comments in your code where necessary and provide a clear and concise description of your changes in the pull request. + +Testing +Before submitting a pull request, make sure your changes have been tested thoroughly. Include relevant test cases and ensure that existing tests pass. + +Issue tracker +Check the issue tracker for any open issues or feature requests. If you're working on something, please comment on the issue to let others know. + +Code review +All contributions will go through a code review process. Be open to feedback and be willing to make changes if necessary. Code reviews help maintain code quality and consistency. + +Thank you for your contribution! From ab3a49e605098b8b662ea3525751861afed4648a Mon Sep 17 00:00:00 2001 From: NightFlax <71522320+Nightflax@users.noreply.github.com> Date: Fri, 22 Aug 2025 08:19:18 -0600 Subject: [PATCH 3/4] Update README.md Changed the date of the footer by one year --- README.md | 22 +--------------------- 1 file changed, 1 insertion(+), 21 deletions(-) diff --git a/README.md b/README.md index 884d4515d6..2a2b1d78df 100644 --- a/README.md +++ b/README.md @@ -13,24 +13,4 @@ Output simple interest = p*t*r ``` -_© 2022 XYZ, Inc._ - -Please consider the below factors while contributing - -Code Style: -Maintain a consistent code style for readability. - -Documentation: -Ensure well-documented code for effective collaboration. - -Testing: -Thoroughly test your changes before submitting a pull request. - -Issue Tracker: -Check the Issue Tracker for tasks. - -Code Review: -All contributions undergo a code review process. - -Licensing: -Contributions are licensed. +_© 2023 XYZ, Inc._ From 400b363b238f3a6ca3b0f7d5a5ce025de489abd4 Mon Sep 17 00:00:00 2001 From: NightFlax <71522320+Nightflax@users.noreply.github.com> Date: Fri, 22 Aug 2025 08:24:45 -0600 Subject: [PATCH 4/4] Update README.md Reverted changes from date in README file --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2a2b1d78df..b103466139 100644 --- a/README.md +++ b/README.md @@ -13,4 +13,4 @@ Output simple interest = p*t*r ``` -_© 2023 XYZ, Inc._ +_© 2022 XYZ, Inc._