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

[Developer Video] Understanding CI check failures #4610

Closed
rt4914 opened this issue Sep 22, 2022 · 2 comments
Closed

[Developer Video] Understanding CI check failures #4610

rt4914 opened this issue Sep 22, 2022 · 2 comments
Assignees
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.

Comments

@rt4914
Copy link
Contributor

rt4914 commented Sep 22, 2022

We should create a youtube video for [Developer Video] Understanding CI check failures so that contributors can easily follow the video for better understanding.

@rt4914 rt4914 self-assigned this Jun 6, 2023
@MohitGupta121 MohitGupta121 added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). enhancement End user-perceivable enhancements. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. labels Jun 16, 2023
@rt4914 rt4914 assigned MohitGupta121 and unassigned rt4914 Jun 19, 2023
adhiamboperes pushed a commit that referenced this issue Oct 20, 2023
…& Replace wiki broken links (#5199)

<!-- READ ME FIRST: Please fill in the explanation section below and
check off every point from the Essential Checklist! -->
## Explanation

Fix #5192, #4610 : [Developer Video] Understanding CI check failures &
Replace Wiki broken links

This PR include developer video that explains how to handle failures in
our Continuous Integration (CI) checks in oppia-android. It also
includes the replacement of broken links in our Wiki, improving the
documentation for a smoother developer experience.

<!--
- Explain what your PR does. If this PR fixes an existing bug, please
include
- "Fixes #bugnum:" in the explanation so that GitHub can auto-close the
issue
  - when this PR is merged.
  -->

## Essential Checklist
<!-- Please tick the relevant boxes by putting an "x" in them. -->
- [x] The PR title and explanation each start with "Fix #bugnum: " (If
this PR fixes part of an issue, prefix the title with "Fix part of
#bugnum: ...".)
- [ ] Any changes to
[scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets)
files have their rationale included in the PR explanation.
- [x] The PR follows the [style
guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide).
- [x] The PR does not contain any unnecessary code changes from Android
Studio
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)).
- [x] The PR is made from a branch that's **not** called "develop" and
is up-to-date with "develop".
- [x] The PR is **assigned** to the appropriate reviewers
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).
@adhiamboperes
Copy link
Collaborator

@MohitGupta121, didn't we already complete this?

@MohitGupta121
Copy link
Member

Yes @adhiamboperes by #5199

Rd4dev pushed a commit to Rd4dev/oppia-android that referenced this issue Oct 31, 2023
… failures & Replace wiki broken links (oppia#5199)

<!-- READ ME FIRST: Please fill in the explanation section below and
check off every point from the Essential Checklist! -->
## Explanation

Fix oppia#5192, oppia#4610 : [Developer Video] Understanding CI check failures &
Replace Wiki broken links

This PR include developer video that explains how to handle failures in
our Continuous Integration (CI) checks in oppia-android. It also
includes the replacement of broken links in our Wiki, improving the
documentation for a smoother developer experience.

<!--
- Explain what your PR does. If this PR fixes an existing bug, please
include
- "Fixes #bugnum:" in the explanation so that GitHub can auto-close the
issue
  - when this PR is merged.
  -->

## Essential Checklist
<!-- Please tick the relevant boxes by putting an "x" in them. -->
- [x] The PR title and explanation each start with "Fix #bugnum: " (If
this PR fixes part of an issue, prefix the title with "Fix part of
#bugnum: ...".)
- [ ] Any changes to
[scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets)
files have their rationale included in the PR explanation.
- [x] The PR follows the [style
guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide).
- [x] The PR does not contain any unnecessary code changes from Android
Studio
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)).
- [x] The PR is made from a branch that's **not** called "develop" and
is up-to-date with "develop".
- [x] The PR is **assigned** to the appropriate reviewers
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.
Development

No branches or pull requests

3 participants