RealDevSquad / RealDevSquad/website-backend

Implement GitHub Issue Editing Sync Functionality

Open
#2,173 0 comments 0 reactions 1 assignee View on GitHub

@Achintya-Chatterjee is already working on this.

Since Jan 15, 2025.

Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

Issue Description

Currently, there is a one-way flow of data from the RDS GitHub repository to the RDS TCR page:

  • If a new issue is added to the RDS GitHub repository, it is successfully reflected on the RDS TCR page. (On task page, it's not synced)
  • Any changes made to GitHub issues are not synced with RDS Tasks and any changes made directly on RDS Tasks and TCR (e.g., updates by the task assignee or assigned member) do not sync to the corresponding GitHub issue, creating an incomplete synchronization process.
Expected Behavior

Any changes made to a task on RDS Tasks or TCR by the task assignee or the assigned member, these updates should be automatically reflected in the corresponding GitHub issue on the RDS GitHub repository. And also any changes made on GitHub issue on the RDS GitHub repository it should reflect on RDS Task and TCR. This ensures two-way data synchronization between RDS Tasks/TCR and GitHub Issues.

Current Behavior

Currently, there is a one-way data flow from the RDS GitHub repository to the RDS TCR page. New issues and any updates in GitHub are reflected on the RDS TCR page, but the same changes are not reflected on RDS task page. Any Changes made on TCR/Task page are not synced back to GitHub issue. This is creating an incomplete synchronization.

Screenshots

NA

Reproducibility
  • This issue is reproducible
  • This issue is not reproducible
Steps to Reproduce
  1. Modify a task on RDS Tasks (e.g., update the task title, description, or status) by the assigned member or task assignee.
  2. Observe that the corresponding GitHub issue does not reflect these changes.
Severity/Priority
  • Critical
  • High
  • Medium
  • Low
Additional Information
Checklist
  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.