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

Refactor one thing #42

Open
dpshelio opened this issue Dec 2, 2024 · 0 comments
Open

Refactor one thing #42

dpshelio opened this issue Dec 2, 2024 · 0 comments
Labels
week09 Structure and design

Comments

@dpshelio
Copy link
Contributor

dpshelio commented Dec 2, 2024

Continuing with the example you reviewed before and the discussion you had (issues #39, #40, #41). Let's implement at least one improvement.

  1. First, take around 5 minutes to plan your changes.
  2. Once that is done, start making changes according to your plan.

To get the files on your computer and push them back, remember to:

  1. Fork the repository
  2. Clone your fork
  3. (create branch, make changes, commit...)
  4. Push back to your fork

You can submit a Pull Request for the original repository when you have made some change.

  • You don't have to wait until they're all done!
  • Target the main branch of the original repository
  • Indicate the example you have worked on in the title of the PR, e.g., "Boids: rename variables"
  • Link your PR to this issue adding Answers UCL-COMP0233-24-25/RSE-Classwork#42
  • If you have more time, add more commits to your branch so they are included in the pull request (update the title accordingly if needed)
@dpshelio dpshelio added the week09 Structure and design label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
week09 Structure and design
Projects
None yet
Development

No branches or pull requests

1 participant