Weekly report
| Student: | mustafa.sarikaya@student.ucll.be |
| Study: Professional Bachelor | Major: ICT |
| Company: Yappa | City: Bilzen |
Activities Week 03 (23/02/2026 - 27/02/2026)
Monday (Day 11)
Today I had a meeting planned with Laura Schrijvers, the Project Manager. We discussed the currently resolved user stories and the next steps for the MVP. I brought up the fact that 25 Jira tickets have been resolved and are contained in a sprint I called Sprint 0. This sprint captures all changes made during the POC phase in the development branch. I held off on merging into main since the dev team had 12 pull requests ready for review. Due to the high volume, the team decided to wait on Wesley's opinion on how to reviews will be handled.
Afterwards, I continued working on organizing the tickets for the MVP. I added more user stories to Jira that were more specific than the initial 100 tickets created before I had fully understood the project requirements and concept.
Tuesday (Day 12)
Today I worked on the PRs on my GitHub repository which are ready for review merged with main, I also set up GitHub Actions scripts for syncing Jira tickets with the VitePress site.
Today was also the day of this month's Yappawadoeda, a monthly gathering at noon where Yappa provides lunch while team presentations are showcased. During the event, I gave my own introduction to the development team as the new intern.
Afterwards, I continued working on Jira tickets; I now had 250 user stories in total. I plan to refine these tickets based on feedback from the team and stakeholders. Right before the end of the day, Wesley stopped by to ask about the project's progress. I explained the POC status and my MVP goals. He requested a summary of the MVP's requirements and features, so I began working on that and provided it to him by day's end.
Wednesday (Day 13)
Today I joined the repository created under Yappa's organization on GitHub, which will store the final code. My personal repository serves as the development repository, while the Yappa repository serves as the production repository. I spent time organizing the PRs and tidying up. I reduced the count to 6 and assigned Jira tickets to each. While organizing, I also performed general maintenance: cleaning up code, fixing GitHub Actions workflows, and addressing bugs and issues I noticed in the POC.
Eventually, these PRs will have to be reviewed by Davy Dewit, after which they will be merged with main.
Thursday (Day 14)
Davy provided me with two additional GitHub repositories under the Yappa organization today—one for the Symfony backend and one for the Slack bot.
Currently, all my POC code changes are in my monorepo, which contains a docs/ directory for the VitePress website, a backend/ directory for the Symfony server, and a slack/ directory for the TypeScript Slack Bolt app. To maintain clean commit histories across my private repo and the Yappa sub-repos, I implemented a specific workflow structure.
I split the dev branch into three separate branches, with my monorepo containing all code changes from the three directories while the sub-repos contain only their respective code. This ensures pull requests occur in the sub-repos themselves, and after resolving Jira items, I merge the main branches back into the monorepo.
I also got access to the hosting environment that Yappa uses. My plan is to make this the live production server for the Slack and Symfony instances.
Additionally, I created a new Slack bot called YapHub Dev for development and testing, while the production bot will contain only approved and merged changes. I spent the entire day migrating code and configurations from the development servers to the production Yappa servers.
Friday (Day 15)
I had to restructure my pull requests today. When Davy provided the two Yappa repositories yesterday, the original 6 PRs could not merge due to diverging commit histories. After reorganizing, I created 12 PRs for the Slack repository and 17 for the Symfony repository, totaling 29 PRs encompassing all POC changes from weeks 1 and 2.
In the afternoon, I met with Laura and Davy to discuss the project's current status and clarify open questions. I also raised concerns about structuring upcoming sprint tickets and expressed worry that PR reviews could become a bottleneck, delaying progress on other tickets. The team assured me they would prioritize review throughput to keep development moving forward.
New skills
- Git workflow management (mono repo and sub-repos)
- GitHub Actions CI/CD pipeline configuration for Jira synchronisation
- Managing and structuring pull requests across repositories
Useful data
- Yappa GitHub Organisation: github.com/yappabe
- VitePress Documentation (Cloudflare Pages): https://knowledgehub-aks.pages.dev
- Jira Board: 250 user stories tracked across epics
- Production hosting environment provisioned by Yappa
Remarks
This week was focused on transitioning the project from a personal development setup to Yappa's organisational infrastructure. Setting up the multi-repository workflow and moving code to the production servers were necessary steps before development of the MVP could begin. The 29 pull requests covering the POC work are now awaiting review, which will unblock the start of Sprint 1.