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

Fix horizontal scroll bug #35

Merged
merged 2 commits into from
Aug 1, 2024
Merged

Fix horizontal scroll bug #35

merged 2 commits into from
Aug 1, 2024

Conversation

Firebird1029
Copy link
Member

Fix horizontal scroll bug

Problem

On mobile, there is a horizontal scroll caused by text that overflows the cards. By adding an overflow CSS property, this removes the issue. Some other compile-time issues were also resolved.

Solution

Also, some of the issues brought up in #23 do not appear when the website is tested locally, such as the menu. The deployed website at dsacms.github.io/open is probably just an outdated build.

Copy link
Contributor

@decause-gov decause-gov left a comment

Choose a reason for hiding this comment

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

@IsaacMilarky and @natalialuzuriaga should give this a look also now that we're all back. projects.liquid looks legit, but I'm not sure about repos.js. Thoughts?

"EASi is a web application supporting the IT governance process at CMS.",
category: "apps",
},
// "CMSgov/easi-app": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we just commenting out this one entry?

Copy link
Member Author

Choose a reason for hiding this comment

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

This entry messes up the script for some reason, I figured the repo was set to private or deleted

Copy link
Contributor

Choose a reason for hiding this comment

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

Aha! I figured it out I reckon. Seems as though the repo has been transferred between CMS orgs! It is now hosted at https://github.com/CMS-Enterprise/easi-app!

easi-app is one of our most active oss projects, so we don't want to just skip or ignore it. For now, could we just manually update/rename the repos.js entry with the new URL/path, and move the associated _data accordingly?

@IsaacMilarky This seems like it will be a relatively rare occurrence, but an edgecase I suppose we should check for and catch? Let's ship this bugfix for now as-is, but file a new ticket for "Check for whether a repo has been transferred between CMS GitHub orgs."

Copy link
Collaborator

Choose a reason for hiding this comment

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

There is an API endpoint to check to see if a repository was moved and it returns the new location so we could set up a method to check for that.

The endpoint is in the format https://api.github.com/repos/<repo_group>/<repo_name> and will tell you the new location if the repository has been moved.

For now we can just rename it but we could have some additional resolution logic in theory.

site/projects.liquid Show resolved Hide resolved
@Firebird1029 Firebird1029 requested a review from decause-gov July 29, 2024 17:12
Copy link
Contributor

@decause-gov decause-gov left a comment

Choose a reason for hiding this comment

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

LGTM +1 🚢 🐛 🔧

@IsaacMilarky IsaacMilarky merged commit 07d68bb into main Aug 1, 2024
2 checks passed
@natalialuzuriaga
Copy link
Collaborator

@Firebird1029 yup you are completely right with the deployed website being an outdated build. For some reason, the deploy jobs was skipped in the last couple of PRs when main was updated but now it looks like that job is running fine now and the website is up to date

@Firebird1029
Copy link
Member Author

@natalialuzuriaga Something weird is happening -- looks like none of the bugs are fixed at https://dsacms.github.io/open/projects/ but the deploy job (or one of the jobs) definitely ran because, on the website, I see the repo I created yesterday in the DSACMS Github org, so the script ran very recently. But all the frontend problems are still there despite working locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants