-
Notifications
You must be signed in to change notification settings - Fork 23
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
Lines not being ordered correctly #1763
Comments
I opened up issues to correct these specific errors, but as @Harjot1Singh mentioned, there should be a check implemented for this. |
|
Sri Dasam Granth Ji Sri Guru Granth Sahib Ji
|
@sarabveer please let me know how you want to proceed with this, Also advise or bug fix branch for this issue. |
@SSAT I would need to look into how to change the page number without breaking CI builds. It should be an easy process. For branches, our usual process is to create a new branch off of |
It would be preferable to have shorter-living PRs (so no wip/draft PRs for weeks at a time, but one weekend duration is okay), so if need be make the PR smaller so as to complete it earlier. This makes it easier for reviewers too. Forking is also encouraged and making branches in your personal repos. See desktop contributing for more details |
To correct them you're right. You could work on and resolve this issue
today from data perspective. Just need those issues to be resolved in order
to consume correct data.
…On Wed, May 27, 2020, 22:47 Sarabveer Singh ***@***.***> wrote:
Depends on fix for #1481 <#1481>
via #1483 <#1483>
AFAIK this issue isn't dependent on anything. Just page numbers need to be
corrected.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1763 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLZ3B7UXA3EZ3F4UTWKFOTRTXGCRANCNFSM4M46LMUQ>
.
|
Loads of page number mistakes in Raag Aasa. The iGurbani metadata that was initially imported seems to be problematic. |
|
The text was updated successfully, but these errors were encountered: