Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track changes to be synced from snakeyaml-engine #260

Closed
krzema12 opened this issue Oct 28, 2024 · 0 comments
Closed

Track changes to be synced from snakeyaml-engine #260

krzema12 opened this issue Oct 28, 2024 · 0 comments
Assignees

Comments

@krzema12
Copy link
Owner

This project was forked from https://bitbucket.org/snakeyaml/snakeyaml-engine/. Even though it was ported to Kotlin, the general structure is still very close to snakeyaml-engine. Right now we sync changes from that project periodically, but there's no set cadence nor mechanisms that help us.

As the first step, for the sake of monitoring if there are any changes to be ported over to our project, I suggest the following approach:

  1. Have a file with commit hash of snakeyaml-engine pointing to the latest commit that was already ported to snakeyaml-engine-kmp.
  2. Have a workflow that periodically (every day/week?) calculates how many commits there are between the tip of the master branch and the commit stored in the file in our project.
  3. Surface this number in e.g. a badge in README, with a note that ideally it should be 0, and with notes how to proceed if it's not 0.
@krzema12 krzema12 self-assigned this Oct 28, 2024
krzema12 added a commit that referenced this issue Oct 28, 2024
Part of #260.

Adding such simple workflow to be able to run it through the UI, and
further iterate on it.
krzema12 added a commit that referenced this issue Nov 8, 2024
Part of #260.

Thanks to this, we'll be able to easily see if there are some changes to
sync from the upstream.
krzema12 added a commit that referenced this issue Nov 8, 2024
Part of #260.

Thanks to this, we can preview what commits need to be synced.
@krzema12 krzema12 closed this as completed Nov 8, 2024
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

No branches or pull requests

1 participant