---
# System prepended metadata

title: '2022-02-03 Eiffel monthly community meeting: New source change events'
tags: [Monthly Community Meetings]

---

###### tags: `Monthly Community Meetings`

# 2022-02-03 Eiffel monthly community meeting: New source change events

## Attendees

- Erik Sternerson, doWhile
- Magnus Bäck, Axis Communications
- Mattias Linnér, Ericsson
- Sven Selberg, Axis Communications

## Discussions

- Why do we need to send new events just because a branch is created?
    - The current SCC/SCS events don't model the (Git) reality that well, and regardless of what you do you'll run into weirdness if you attempt to model reality with those events.
- With too much metadata (commit message, author, etc) in the Eiffel events there might be confidentiality issues. We probably shouldn't impose too many strict rules about which information must be included in source change events.
- Triggering workflows based on comments, votes, or similar is an interesting ues case. Could maybe be solved with CLM events. See [github.com/eiffel-community/eiffel#236](https://github.com/eiffel-community/eiffel/issues/236).

## Actions

- Further scenarios to describe:
    - GitHub PR scenario, especially with multiple states of the PR branch.
    - Difference merge cases like squash merge and merge commit.
- To which event type should inbound links from e.g. CD connect to? The commit or the branch update? Hardly the commit since it doesn't contain information about the repository URI.
- BASE and PREVIOUS_VERSIONS links for SCC are inconsistent and poorly documented.
