Skip to content

Conversation

@pamoroso
Copy link
Contributor

An update to the News and Status Reports page that links to the YouTube videos we posted in Sep 2025 and Ryan Burnside's Interlisp project for the Autumn Lisp Game Jam 2025.

Link to our YouTube videos posted in Sep 2025 and Ryan Burnside's Interlisp project for the Autumn Lisp Game Jam 2025.

Signed-off-by: Paolo Amoroso <info@paoloamoroso.com>
@pamoroso pamoroso requested review from masinter and stumbo November 13, 2025 11:20
@stumbo stumbo merged commit e748af6 into Interlisp:main Nov 13, 2025
@pamoroso
Copy link
Contributor Author

After this PR was merged, using GitHub's web interface I synced the corresponding branch of my fork and now there's a pamoroso:pa5-sep-nov-2025-updates had recent pushes 2 minutes ago Compare & pull request button both here and in my fork. Any advice on how to proceed? Should I delete the branch in my fork?

@stumbo
Copy link
Member

stumbo commented Nov 14, 2025

@pamoroso I don't use the web interface and so I may be off on what happened. What I believe happened - you created the PR, I reviewed, approved and merged it. That action added your changes to main. You then merged main back into your branch. This action added two commits - the merged PR and a merge commit. The result is your branch now has two new commits to it. GitHub sees that there are changes to your branch the two commits (GitHub is calling them pushes).

My advice is to delete the branch. It has served its purpose and has no real value. If you want to add new updates, I would create a new branch from the updated main and go from there.

@pamoroso
Copy link
Contributor Author

Thanks, I deleted the branch and now my repo is up to date.

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.

2 participants