[Office Hours] How to contribute to the repos you've set up for us

[kkellybonilla]

Related Discussion

Hi CS 342 Team!

To contribute to the repos that you've set up for us, are we to fork them and create pr's that way, or will we be added as collaborators so that we can push our branches and make pr's from our branches to main? Or are we expected to create a repo of our own and the repo that you all have set up for us is just to play around with?

Reproduction

N/A

Additional context

No response

Code of Conduct

• I agree to follow this course's Code of Conduct and Contributing Guidelines

[PSchmiedmayer]

Hi @kkellybonilla,

Happy to help!

You and your team members are all part of the https://github.com/orgs/CS342/teams/2025-stanford-360 team.
The team has write access to the https://github.com/CS342/2025-Stanford-360 repository.

You can create feature branches directly in the repository, push to the newly created branches, and create a pull request to propose your changes to be merged in the main branch. It requires that all your builds are passing and you need to ask for reviews from your team members before you can merge the PR. You can not directly push to the main branch of the repository.

Please check out the information we shared about these workflows in the lectures 3B and 4A. We would recommend using GitHub Desktop, might make your life a bit easier to deal with git.

[PSchmiedmayer]

@kkellybonilla Could you resolve your issue?

[mmervecerit]

Hello @PSchmiedmayer, I tried to merge the approved PR, and the builds also seem OK. However, the repo still doesn't allow pushing to the main, what could be the reason for that? See PR here

[PSchmiedmayer]

Sorry about this @mmervecerit!
There was a permissions error in allowing you to merge the PR. I have resolved it; great job with merging the first PR!

[mmervecerit]

thank you @PSchmiedmayer! just merged it, but shipping it to TestFlight automatically, there was an error. I don't know what exactly the issue is, first time dealing with deployments. -> https://github.com/CS342/2025-NeutroFeverGuard/actions/runs/13061897123

Maybe related to this?:

Failure Reason: Application info provider (FBSApplicationLibrary) returned nil for "edu.stanford.cs342.2025.neutrofeverguard"
User Info: {
    BSErrorCodeDescription = NotFound;
}

[PSchmiedmayer]

@mmervecerit Sorry for the late response. The cause for the build error can be found at the bottom of the output: https://github.com/CS342/2025-NeutroFeverGuard/actions/runs/13061897123/job/36454636852#step:17:6529. It seems like one test is failing on the runners and we have seen the same test failing across multiple apps. I will look into this; the easier thing is to re-run the job as it seems to be a flaky test.

[PSchmiedmayer]

@mmervecerit We have taken a closer look at these issues and fixed them in our template application with the following PR: StanfordSpezi/SpeziTemplateApplication#98.

The best way to replicate the changes would be to:

1. Update all dependencies to the latest version in Xcode and committing all the updated project files + Package.resolved file. You need to run File -> Swift Packages -> Update to Latest Package Versions in Xcode.
2. Modifying the UI tests to be a bit more stable and adjust to the latest changes in all the dependencies, mostly focusing on the diff in:
   a) TemplateApplicationUITests/OnboardingTests.swift
   b) TemplateApplicationUITests/SchedulerTests.swift

[mmervecerit]

Thank you so much @PSchmiedmayer, working on the changes!