Update Feature/issue 608

[snikmas]

Description

Wiki moved to [this main/docs]](https://github.com/Together-100Devs/Together/tree/main/docs), so I updated the url

Type of change

Please select everything applicable. Please, do not delete any lines.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This change requires an update to testing

Issue

• Is this related to a specific issue? If so, please specify:
  fixed header buttons on /calenadr #608 (review)

Checklist:

• This PR is up to date with the main branch, and merge conflicts have been resolved
• I have executed npm run test and npm run test:e2e and all tests have passed successfully or I have included details within my PR on the failure.
• I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
• 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
• My changes generate no new warnings

[DevinCLane]

So normally it's better to just add the changes to the currently open PR, could you do that? feel free to ask questions if you're not sure how to.

you can just make changes and then push to that same branch and it will show in the same PR

[snikmas]

So normally it's better to just add the changes to the currently open PR, could you do that? feel free to ask questions if you're not sure how to.

you can just make changes and then push to that same branch and it will show in the same PR

Okay, yeah, I didn’t really understand how to add new changes.
So usually you just need to add changes to the first branch and push them? But I’ve already deleted it, so I’m not sure if it’s possible to restore it

[merrua]

You have a file called "cd" that looks like it should not be in your pull request.
You have a file called git that shouldn't be checked in.
Take a look at the .gitignore file that prevents unwanted files from being checked in.

[snikmas]

You have a file called "cd" that looks like it should not be in your pull request. You have a file called git that shouldn't be checked in. Take a look at the .gitignore file that prevents unwanted files from being checked in.

Okay, I’ve just uncommitted them, no idea how they got in

[DevinCLane]

looks good, can you squash this down to one commit then we're good to merge

[merrua]

@snikmas Did you see Devins comment about squashing the commits?

[snikmas]

@snikmas Did you see Devins comment about squashing the commits?

now I see it. I will try to squash it

[DevinCLane]

@snikmas checking in on this