-
Notifications
You must be signed in to change notification settings - Fork 219
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
chore: README updated #1396
chore: README updated #1396
Conversation
Thanks for the pull request, @CodeWithEmad! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1396 +/- ##
==========================================
+ Coverage 88.76% 88.83% +0.07%
==========================================
Files 305 307 +2
Lines 5234 5268 +34
Branches 1327 1304 -23
==========================================
+ Hits 4646 4680 +34
Misses 572 572
Partials 16 16 ☔ View full report in Codecov by Sentry. |
@CodeWithEmad Thank you for this contribution! We've got a green build so I'm marking it as ready for review now, but let me know if you had plans to work on it some more. |
Hey @openedx/2u-aurora team, this PR is ready for review. |
If @openedx/2u-aurora team maintains this repo, let me update the |
5f99de2
to
03eefcb
Compare
@CodeWithEmad Sounds good! BTW, if a repo is maintained, it'll have the maintainer(s) listed as |
Got it. |
Hi @openedx/2u-aurora team, could you have a look at this PR please? |
Reached out to core contributors via Slack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, please address the point about catalog-info and we can get this merged.
README.rst
Outdated
|
||
This is the Learning MFE (micro-frontend application), which renders all | ||
learner-facing course pages (like the course outline, the progress page, | ||
actual course content, etc). | ||
|
||
Please tag **@edx/engage-squad** on any PRs or issues. Thanks. | ||
Please tag **@openedx/2u-aurora** on any PRs or issues. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove this line, or point at the https://github.com/openedx/frontend-app-learning/blob/master/catalog-info.yaml file. All repos are migrating to using catalog-info
so let's not make it error prone by duplicating the info.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll remove it but I had PRs in the past stuck in review for months before I mentioned someone. Also, this pattern (mentioning the owner for review) is repeated in other repos like Profile MFE. What's the best solution here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CodeWithEmad It's completely fine to ping repo maintainers for review if they don't respond to a PR within a week or two.
I think @sarina's comment was more about not putting information about who owns a repo into two places. (Because it's easy to forget updating it in both places when it changes, especially when there's a widely accepted default for where this information should go.)
If you wanted to update the README of this repo to mention that PR authors should ping repo maintainers for review, you could still do that. Just keep it neutral -- i.e., instead of explicitly mentioning the current maintainer(s) in the README, tell the reader to check https://github.com/openedx/frontend-app-learning/blob/master/catalog-info.yaml to find out who to ping 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly right, it's about duplicating information. I like @itsjeyd 's suggestion of pointing people to the catalog-info.yaml
file.
@@ -1,25 +1,22 @@ | |||
##################### |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just FYI the overlines are not wrong, it's OK to leave them in. But OK that you've removed them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I am aware of that. I am just trying to ensure all the documents have a consistent appearance.
README.rst
Outdated
|
||
Example: https://support.edx.org/hc/en-us/articles/360000038428-Entering-math-expressions-in-assignments-or-the-calculator | ||
|
||
SUPPORT_URL_ID_VERIFICATION | ||
A link that explains how to verify your ID. Shown in contexts where you need | ||
to verify yourself to earn a certificate. The example link below is probably too | ||
edx.org-specific to use for your own site. | ||
edx.org-specific to use for your site. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this sentence better without this change, but will not block merging on this feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no objections to it. I'll revert the change.
- code blocks added. - heading issues fixed. - small typos fixed.
03eefcb
to
b01a129
Compare
@CodeWithEmad 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
This will fix some issues in the readme:
Also in the readme said:
I wanted to tag @edx/engage-squad but looks like this account is deleted. should I update that too?