Skip to content

Conversation

@Naragod
Copy link
Contributor

@Naragod Naragod commented Jan 20, 2026

Proposed Changes

We have sped up student access to repositories by changing the way in which we query information. Previously we were making N + 1 queries. One query to obtain the number of N groups in each assignment, and subsequen N queries to grab all of the students in each group.

We now instead, grab all of the associated group and student information and filter it out in memory to speed up access.

Screenshots of your changes (if applicable)
Associated documentation repository pull request (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue) X
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

  • I have performed a self-review of my changes.
    • Check that all changed files included in this pull request are intentional changes.
    • Check that all changes are relevant to the purpose of this pull request, as described above.
  • I have added tests for my changes, if applicable.
    • This is required for all bug fixes and new features.
  • I have updated the project documentation, if applicable.
    • This is required for new features.
  • If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

  • I have updated the project Changelog (this is required for all changes).
  • I have verified that the pre-commit.ci checks have passed.
  • I have verified that the CI tests have passed.
  • I have reviewed the test coverage changes reported by Coveralls.
  • I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

@Naragod Naragod added this to the v2.9.1 milestone Jan 20, 2026
@Naragod Naragod changed the title Ticket 575 improve git repo access TICKET-575: Improve git repo access Jan 20, 2026
@Naragod Naragod marked this pull request as draft January 20, 2026 04:41
@Naragod Naragod force-pushed the TICKET-575_improve_git_repo_access branch from 7306bbc to f425741 Compare January 20, 2026 15:46
@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 21159705914

Details

  • 33 of 33 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.004%) to 91.612%

Totals Coverage Status
Change from base Build 21158214422: -0.004%
Covered Lines: 44162
Relevant Lines: 47398

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants