Use the right font in _app.css #23

New Issue

2021-05-08T15:04:04-04:00

a3thakra commented

2021-05-08 15:04:04 -04:00

(Migrated from git.uwaterloo.ca)

This is a great resource: https://developer.mozilla.org/en-US/docs/Learn/CSS/Styling_text/Web_fonts

We should apply the font to all elements: * { font-family: poppins; }.

This is a great resource: https://developer.mozilla.org/en-US/docs/Learn/CSS/Styling_text/Web_fonts We should apply the font to all elements: `* { font-family: poppins; }`.

a3thakra commented

2021-05-08 15:07:46 -04:00

(Migrated from git.uwaterloo.ca)

changed the description

a3thakra commented

2021-05-08 15:10:07 -04:00

(Migrated from git.uwaterloo.ca)

changed the description

a3thakra commented

2021-05-08 15:33:45 -04:00

(Migrated from git.uwaterloo.ca)

changed title from Use the right font _app.css to Use the right font {+in +}_app.css

changed title from **Use the right font _app.css** to **Use the right font {+in +}_app.css**

a3thakra commented

2021-05-08 15:34:03 -04:00

(Migrated from git.uwaterloo.ca)

mentioned in merge request !2

a258wang commented

2021-05-09 00:42:56 -04:00

(Migrated from git.uwaterloo.ca)

mentioned in merge request !3

a3thakra commented

2021-05-10 23:57:56 -04:00

(Migrated from git.uwaterloo.ca)

mentioned in merge request !6

a3thakra commented

2021-06-09 21:28:00 -04:00

(Migrated from git.uwaterloo.ca)

You should name your branch based on what you're doing. There are two schools (more, but these are the common ones):

Use feat/feature-name for features and chore/chore-name for chores
Use linna-feature-name for features and linna-chore-name for chores

I prefer the use the second one, but if you choose to use the first one - make sure you use feat/ and chore/ properly. For example, this will be considered a chore, and not a new feature. The second approach doesn't really care if you're working on a feature or a chore, which is why I like it more haha!

You should name your branch based on what you're doing. There are two schools (more, but these are the common ones): - Use `feat/feature-name` for features and `chore/chore-name` for chores - Use `linna-feature-name` for features and `linna-chore-name` for chores I prefer the use the second one, but if you choose to use the first one - make sure you use `feat/` and `chore/` properly. For example, this will be considered a chore, and not a new feature. The second approach doesn't really care if you're working on a feature or a chore, which is why I like it more haha!

a3thakra commented

2021-06-09 21:31:05 -04:00

(Migrated from git.uwaterloo.ca)

changed title from MiniEventCard drop down icon styling{- fix-} to {+Fix +}MiniEventCard drop down icon styling

changed title from **MiniEventCard drop down icon styling{- fix-}** to **{+Fix +}MiniEventCard drop down icon styling**

a3thakra commented

2021-06-09 21:31:05 -04:00

(Migrated from git.uwaterloo.ca)

changed the description

a3thakra commented

2021-06-09 21:34:30 -04:00

(Migrated from git.uwaterloo.ca)

Also try not to reuse branch names

a3thakra commented

2021-06-09 21:35:34 -04:00

(Migrated from git.uwaterloo.ca)

approved this merge request

a3thakra commented

2021-06-09 21:36:13 -04:00

(Migrated from git.uwaterloo.ca)

added 9 commits

d2ea04d8...dc0cc390 - 8 commits from branch main
3ff0f195 - Merge remote-tracking branch 'origin/main' into feat/mini-event-card

Compare with previous version

added 9 commits <ul><li>d2ea04d8...dc0cc390 - 8 commits from branch <code>main</code></li><li>3ff0f195 - Merge remote-tracking branch 'origin/main' into feat/mini-event-card</li></ul> [Compare with previous version](/csc/website/-/merge_requests/23/diffs?diff_id=59008&start_sha=d2ea04d84cf6ab99413ee9843a3231e5b1a3317c)

a3thakra commented

2021-06-09 21:36:21 -04:00

(Migrated from git.uwaterloo.ca)

enabled an automatic merge when the pipeline for 3ff0f1951a succeeds

enabled an automatic merge when the pipeline for 3ff0f1951a6bf0f29dec088b325e67036f726871 succeeds

Sign in to join this conversation.