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

Update Team Meeting Data on Events Page to show Meeting Frequency #7088

Conversation

terrencejihoonjung
Copy link
Member

Fixes #6920

What changes did you make?

  • added *This meeting is not weekly, check project link for more details. at the bottom of the right-col-content.html
  • conditionally rendered an asterisk if the event's description was not empty within right-col-content.js

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

  • to indicate that an asterisk means that the meeting is not necessarily weekly
  • when the event description is not empty, it contains information about an alternative meeting schedule. By rendering an asterisk when the event description is not empty, we indicate that the meeting is not weekly.

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

Visuals before changes are applied before
Visuals after changes are applied after

terrencejihoonjung and others added 30 commits June 20, 2024 19:46
* Update issue-trigger.yml

Changes in prep for Projects Beta migration

* Update issue-trigger.yml

space added to comment

* Update issue-trigger.yml

edits to comment at Team Members

* Update preliminary-update-comment.js

refactoring for PBB migration
* Update pull-request-trigger.yml

edits for PBB migration

* Update pull-request-trigger.yml

remove test branch
* Update schedule-fri-0700.yml

Changes for PBB migration

* Update add-label.js

* Update find-linked-issue.js

For PBB migration

* Update add-label.js

remove refs to personal repo

* Update add-label.js

addressing CodeQL alert

* Update add-label.js

address CodeQL alert
* Update move-closed-issues.yaml

for migration to PBB

* Update sort-closed-issues.js
…#7062)

* remove references to BoP's id from the `untaggedRepoIds` list

* Update contributor and language data

* Revert `github.repository` post GHA test

* Resolve merge conflicts

* Resolve merge conflicts (p2)

---------

Co-authored-by: GitHub Actions Bot <[email protected]>
Copy link

github-actions bot commented Jul 5, 2024

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 terrencejihoonjung-update-team-meeting-data-6920 gh-pages
git pull https://github.com/terrencejihoonjung/website.git update-team-meeting-data-6920

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

https://github.com/terrencejihoonjung/website/blob/update-team-meeting-data-6920/CONTRIBUTING.md  

@github-actions github-actions bot added role: front end Tasks for front end developers Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) P-Feature: Events https://www.hackforla.org/events/ P-Feature: Project Meetings https://www.hackforla.org/project-meetings size: 0.25pt Can be done in 0.5 to 1.5 hours labels Jul 5, 2024
@ha-bach ha-bach self-requested a review July 7, 2024 17:01
@ha-bach
Copy link
Member

ha-bach commented Jul 7, 2024

Review ETA: end of day.
Availability: Sunday, Monday, Wednesday.

Copy link
Member

@ha-bach ha-bach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @terrencejihoonjung,

  • branching looks good
  • relevant linked issue
  • code edit is clean
  • correct changes showed up on my test page

Issues to address:

  • merge conflict with current version of website at _data/external/github-data.json

Overall great work! Just one file is outdated from the current website. Once you've fixed the merge conflict, feel free to @ me and I will review the PR again.

@Thinking-Panda Thinking-Panda self-requested a review July 10, 2024 20:15
@terrencejihoonjung
Copy link
Member Author

Hi @muninnhugin,

Thank you for your feedback! I've handled the merge conflict and updated my branch.

Thank you!

Copy link
Member

@ha-bach ha-bach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course, thank you for your contribution!

@jphamtv
Copy link
Member

jphamtv commented Aug 8, 2024

Hi @Thinking-Panda - Please add your ETA and availability for this review when you get a chance. Thanks!

@t-will-gillis t-will-gillis self-requested a review August 18, 2024 03:34
Copy link
Member

@t-will-gillis t-will-gillis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @terrencejihoonjung I am able to load this in Docker and cross check with vrms-data.json to see that whenever a meeting lists a description, an * is rendered on the "Events" page.

Great job, and thanks for taking care of this.

@t-will-gillis t-will-gillis merged commit 5cb891d into hackforla:gh-pages Aug 18, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium P-Feature: Events https://www.hackforla.org/events/ P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) P-Feature: Project Meetings https://www.hackforla.org/project-meetings role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Development

Successfully merging this pull request may close these issues.

Update Team Meeting data on the Events page to show meeting frequency