Aman Sharma

`spoon-deploy` is disabled if there is no activity on the repository for 60 days. Should we do something about it? For example, push an empty commit once in while.

> Why don't we use an already built solution, [github.com/marketplace/actions/keepalive-workflow](https://github.com/marketplace/actions/keepalive-workflow)? The 60-day problem should be solved by this. This seems like a good idea. I did not look up existing...

Thanks @slarse! I was also thinking of something like this and schedule in every 59 days. On Thu, 3 Nov, 2022, 6:24 pm Simon Larsén, ***@***.***> wrote: > I did...

Hey @AryanMansani ! I have not personally worked with template so I do not have an idea about it, but I would start by referring to [tests](https://github.com/INRIA/spoon/blob/master/src/test/java/spoon/test/template/TemplateTest.java) related to them...

Finally, @I-Al-Istannen ! Congratulations 🎉

Hi! This seems like a bug that we do not consider the package of the type in our `EqualsVisitor`. Something like this should work ```diff diff --git a/src/main/java/spoon/support/visitor/equals/EqualsChecker.java b/src/main/java/spoon/support/visitor/equals/EqualsChecker.java index...

> NominalType wrapper class around a CtType is an elegant solution? This also saves you from walking the complete tree on every equals/hashcode computation, which quickly adds up. So based...

> Doing both (full name and content) Hmmm. If full names are the same, then classes must be the same; if different, they must be different.

I understand your point. I think the beta releases exist because our main release cycles were slow to incorporate a features/fixes on the `master` branch because Martin M did them...

So should I close this PR and submit a PR for removing/disabling beta releases? The goal is that all packages that are pushed to maven central should be reproducible.