Add organizations to user profile

[websebdev]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Added organizations to user profile in the right-hand sidebar.

Related Tickets & Documents

Closes #4672

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• docs.dev.to
• readme
• no documentation needed

[claassistantio]

All committers have signed the CLA.

[rhymes]

Looks nice! Thanks a lot @seb1441!

I've added a screenshot for the other reviewers:

the "organizations" box sits at the top right

[benhalpern]

Looks great!

One issue is that this area is cached within a higher level fragment cache.

As you can see in that cache key, there is a key called github_repos_updated_at which indicates when something has changed about a user's GitHub repos.

We should have a similar attribute on users: organization_info_updated_at which is touched when a user joins a new org.

If you can create that column and add it to this cache key I think we're good to go!

[websebdev]

@benhalpern Oops my bad, I did not notice the higher level fragment cache.
As you suggested, I added the organization_info_updated_at column and cache key that will be touched with after_create and after_destroy callbacks of OrganizationMembership model.

Thank you!

[websebdev]

@rhymes Fixed the 3 failing tests by updating the organization_memberships factory:

• Changed the random user_id and organization_id with real associations.
• Skipped the update_user_organization_info_updated_at callback because stubbed models are not allowed to access the database (touch).

[citizen428]

Very nice PR @seb1441, thanks for this! 👏

[rhymes]

@seb1441 I went ahead and resolved the conflict (the schema file wasn't up to date).

Keep in mind that it's better to use a branching model than to submit PRs from your own master. You can check the contributing guide on how to do it in the future!

[websebdev]

@rhymes Thank you!
Ok for the branching, I will do that for my future PRs :)

Also, I was wondering, when we create a PR, are we expected to keep it up-to-date all the time?
I did rebase from upstream and force push every time that I made a new commit and also had to fix schema conflict in one of these rebases.

[rhymes]

@seb1441 no, unless you need to explicitly merge something from master or rebase a schema conflict you're not expected to track master during the lifetime of the PR :)

Unfortunately the build failed because rails-assets.org is going up and down since yesterday and if we can't reach it we can't build it.

Right now we've merged #5643 to fix that, so I'm afraid you'll have to rebase to make sure.

I'm sorry for the mishap and thanks for the patience!

[mstruve]

Once performance suggestion otherwise this is looking great!

[rhymes]

Left a note about the schema, we're almost there!

Thanks for the patience @sebach1!

[rhymes]

LGTM!

Thanks @seb1441!

[rhymes]

LGTM! Thanks @seb1441!

[mstruve]

LGTM 🚀

[rhymes]

Sorry everyone who reviewed, after merging #5624 a conflict was introduced here. I had to resolve it

[citizen428]

This is great, excellent first contribution @seb1441 😃 Thanks for fixing the conflict @rhymes.

Requested changes have been implemented

[benhalpern]

This is great. Nice work everybody involved in the review.