Update Public Tree Map Slack Link #6514

[elisetvy]

Fixes #6514

What changes did you make?

• Update the Slack link for the Public Tree Maps project

Why did you make the changes (we will use this info to test)?

• So that we have continuity between project Slack links

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

Updating Slack link. No visual changes to the website.

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

From your project repository, check out a new branch and test the changes.

git checkout -b elisetvy-update-project-slack-links-6514 gh-pages
git pull https://github.com/elisetvy/hfla-site.git update-project-slack-links-6514

---

Note that CONTRIBUTING.md cannot previewed locally; rather it should be previewed at this URL:

https://github.com/elisetvy/website/blob/update-project-slack-links-6514/CONTRIBUTING.md  

[gaylem]

Hey @elisetvy Can you add the labels from the issue (#6514) onto this PR? It looks like the workflow that adds those automatically failed. Either something went wrong, or maybe you created the PR in a different way than the workflow expects. Thanks!

[elisetvy]

@gaylem just added the labels. Thanks for the feedback!

[tony1ee]

Review ETA: EOD 04/13/2024
Availability: 12-8 PM SAT

[tony1ee]

Hi @elisetvy, thank you for submitting this pull request.

You did great on:

1. choosing the correct branch for pull request
2. linking the issue
3. making the slack url change as needed for the issue
4. making no visible changes on website for this link change

However, I did find an issue with your request:

• unnecessary changes at line 9 and line 50 for file public-tree-map.md

Review guideline requires changes to be applicable and clean, and unfortunately this does not seem to be met.

Please revert the changes at line 9 and line 50 in the file public-tree-map.md to their original state. Once you've made these adjustments, please push the updated changes to your branch, and I will be happy to review it again.

Thank you for your efforts and cooperation in keeping our project's changes clean and efficient!

[elisetvy]

@tony1ee hi Tony! Thank you for the feedback. Is using 'git revert [id]' the best way to revert a change? I made two changes/commits for this issue. The second change was because I accidentally mistyped something the first time. Should I revert both of these commits and then make the necessary changes? Also curious what would have caused those unnecessary changes in the first place because I didn't touch those lines, but I did notice them get "changed" in the commit history.

[tony1ee]

Hi @elisetvy, you can choose to add another commit that fixes line 9 and line 50 so they appear not changed compared to hackofla:gh-pages (essentially, adding new commits that negate the unnecessary changes)

After you push it to elisetvy:update-project-slack-links-6514, this pull request should automatically update to reflect any new commit, at which point we can move forward with further review.

Thank you for your efforts, looking forward to your updates!

[tony1ee]

To answer your question, one potential reason for these changes made without your explicit actions might be you enabled "format on save" feature on your code editor.
If you mean to keep this feature on but want to avoid unnecessary changes to be committed, you can choose to only add the lines of change you want to make via git add -i (or git add --interactive), instead of adding the whole file to staging, after which you can safely drop the unintended changes.

[elisetvy]

@tony1ee hi Tony, I just made a new commit to negate the unnecessary changes. I think they were caused by me having format on save on, as you said - thanks for the explanation + advice!

[elisetvy]

I made a few commits while still wrestling with my formatter. I think all unnecessary changes have been reverted now.

[LRenDO]

Hi @Beatriz-G! Thanks for volunteering to review this issue! When you have a minute, please add your ETA and Availability. Thanks!

[Beatriz-G]

ETA: EOD 04/17/2024
Availability: 11am-7pm Mon-Th

[Beatriz-G]

Line 34 matches requested changes. Updated public link tree map from messages to archives.

[tony1ee]

Thanks @elisetvy for the effort of making the requested changes, everything looks good now and I am happy to approve this pull request!