These were all relatively simple changes, although I'd like to confirm the new eventType field on the Event data type.

It seems like events can be scoped to different constructs. For example, there are activity events, which is the type of event we are modifying here. There are also events scoped to issues. These two types of events are separate from each other (at least that is my understanding).

Also, each "activity event" has its own payload, which has not been implemented yet.

In 4fcb2b, the -k flag was introduced. It seems that due to an oversight, the tests weren't updated to take this flag into account and are currently failing on a fresh clone of the project. This commit updates the test/mkrc-one-dotfile-arg.t test to account for the new flag.

Fixes #278

The test/mkrc-one-dotfile-arg.t is failing on a fresh clone of the project because of the changes in 4fcb2b7d25354cdacf3c1efd16d4f5bd64dd55e7 adding the -k flag to mkrc.

No PR was merged recently as there weren't no merge-worthy PR!

Interestingly, actions artifacts are not a preview feature in the API, which is good news.

Hi,

Actions API: https://docs.github.com/en/rest/reference/actions I am using this library for pull requests and comments, but now I also need to trigger workflows using "workflow dispatch event".

Should actions API be added to this library? If so, can I help with implementation? Looks like no PRs have been merged lately, so I'm asking for guidance before sending any PRs.

Thanks! I filed https://github.com/haskell-hvr/deepseq-generics/issues/10.

The dependencies

• https://hackage.haskell.org/package/cryptohash-sha1 and
• https://hackage.haskell.org/package/deepseq-generics

still need revisions, so revision on github would still require using allow-newer for them.

Please release a new version including this PR.

Hi @jjb, unfortunately following those steps (using brew at the beginning instead of MacPorts) didn't do much for me. The make step fails outright. I haven't had a ton of time to dig into the failures unfortunately.

When I added a dotfiles with mkrc, after some time I need to create more configuration files in the same directory, and now I need to add the new files to dotfiles for management, I used mkrc to add the whole directory again, and then the already added The configuration file is added again and the final file is not accessible. It is recommended to add a check to filter previously added configuration files. (当我使用 mkrc 添加了一个 dotfiles 后，过了一段时间又需要在同一个目录下新建了多个配置文件,现在需要将后面新建的文件加入到 dotfiles进行管理，我使用了 mkrc 又将整个目录进行了一次添加，这时就会将已经添加过的配置文件再次添加，访问不到最终文件。建议添加一个检查，用于过滤以前添加过的配置文件。)

Process (过程)：

mkrc -t test .config/test

ls -l .config/test
... config -> ~/.dotfiles/tag-test/config/test/config

ls -l .dotfiles/tag-test/config/test/
... config



touch .cofig/shell
mkrc -t test .config/test
ls -l .config/test
... config -> ~/.dotfiles/tag-test/config/test/config
... test/

ls -l .config/test/test/
... config -> ~/.dotfiles/tag-test/config/test/test/config
... shell -> ~/.dotfiles/tag-test/config/test/test/shell

ls -l .dotfiles/tag-test/config/test/
... config
... test/

ls -l .dotfiles/tag-test/config/test/test
... config -> /home/eonun/.dotfiles/tag-test/config/test/config
... shell

config will not find the shell（config找不到shell）

I guess I'm just saying a lot of the preview APIs are quite stable ie. not changed for multiple years, as you listed that as why you don't want the PR. Not saying you should support them, just providing info on the API stability thing.

Regardless, it is poor form from GitHub I agree, I don't understand how something can be in preview and unchanged for 4 years :confused:

@AlistairB so what? Why it's still in preview and not "graduated" for 4.5 years. We don't know.

FWIW, a lot of the github preview APIs are quite stable. For example, the projects api has been out for 4.5 years. Apparently it was only updated once about a month after release.

Hm, I'm not sure what changed since the time I tried above, but I tried again with this recipe and it did work 🎉 https://gist.github.com/jjb/45c129380e2f344df19b618e1f0075b9

@brandoncordell maybe something analogous will work for you

It does not remove it from RCM, though. You need to remove the file in the dotfiles dir. If you are using git : git rm ~/.dotfiles/vimrc

Really appreciated to have a fingerprint signing implemented!

Hi there, really love andOTP. Thank you for the great work! Generally, I'd like to support the android auto fill in request. But if not easily to implement, you may consider to change the behaviour of the option "switch to background after copying" into "switch to task switcher after copying". This would enhance using andOTP to a more fluent experience.

here's what I get trying to build manually

➔ make
depbase=`echo src/gitsh.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
	gcc -DPACKAGE_NAME=\"gitsh\" -DPACKAGE_TARNAME=\"gitsh\" -DPACKAGE_VERSION=\"0.14\" -DPACKAGE_STRING=\"gitsh\ 0.14\" -DPACKAGE_BUGREPORT=\"[email protected]\" -DPACKAGE_URL=\"\" -DPACKAGE=\"gitsh\" -DVERSION=\"0.14\" -I.  -DGITSH_RB_PATH="\"/usr/local/share/gitsh/ruby/gitsh.rb\""   -g -O2 -MT src/gitsh.o -MD -MP -MF $depbase.Tpo -c -o src/gitsh.o src/gitsh.c &&\
	mv -f $depbase.Tpo $depbase.Po
gcc  -g -O2   -o gitsh src/gitsh.o
sed -e 's|@RUBY[@]|/opt/local/bin/ruby|g' -e 's|@rubylibdir[@]|/usr/local/share/gitsh/ruby/lib|g' -e 's|@pkgsysconfdir[@]|/usr/local/etc/gitsh|g' -e 's|@gemsetuppath[@]|/usr/local/share/gitsh/vendor/gems/setup.rb|g' -e 's|@PACKAGE_VERSION[@]|0.14|g' ./src/gitsh.rb.in > src/gitsh.rb
chmod +x src/gitsh.rb
sed -e 's|@RUBY[@]|/opt/local/bin/ruby|g' -e 's|@rubylibdir[@]|/usr/local/share/gitsh/ruby/lib|g' -e 's|@pkgsysconfdir[@]|/usr/local/etc/gitsh|g' -e 's|@gemsetuppath[@]|/usr/local/share/gitsh/vendor/gems/setup.rb|g' -e 's|@PACKAGE_VERSION[@]|0.14|g' ./man/man1/gitsh.1.in > man/man1/gitsh.1
sed -e 's|@RUBY[@]|/opt/local/bin/ruby|g' -e 's|@rubylibdir[@]|/usr/local/share/gitsh/ruby/lib|g' -e 's|@pkgsysconfdir[@]|/usr/local/etc/gitsh|g' -e 's|@gemsetuppath[@]|/usr/local/share/gitsh/vendor/gems/setup.rb|g' -e 's|@PACKAGE_VERSION[@]|0.14|g' ./man/man5/gitsh_completions.5.in > man/man5/gitsh_completions.5
sed -e 's|@RUBY[@]|/opt/local/bin/ruby|g' -e 's|@rubylibdir[@]|/usr/local/share/gitsh/ruby/lib|g' -e 's|@pkgsysconfdir[@]|/usr/local/etc/gitsh|g' -e 's|@gemsetuppath[@]|/usr/local/share/gitsh/vendor/gems/setup.rb|g' -e 's|@PACKAGE_VERSION[@]|0.14|g' ./lib/gitsh/version.rb.in > lib/gitsh/version.rb
cd ext/gitsh && /Library/Developer/CommandLineTools/usr/bin/make
compiling src/line_editor.c
src/line_editor.c:1622:5: warning: incompatible function pointer types passing 'VALUE (VALUE, VALUE)' (aka 'unsigned long (unsigned long, unsigned long)') to parameter of type 'VALUE (*)(VALUE)' (aka 'unsigned long (*)(unsigned long)') [-Wincompatible-function-pointer-types]
    rb_define_singleton_method(mLineEditor, "completer_word_break_characters",
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/local/include/ruby-2.7.0/ruby/intern.h:1218:137: note: expanded from macro 'rb_define_singleton_method'
#define rb_define_singleton_method(klass, mid, func, arity) rb_define_singleton_method_choose_prototypem3((arity),(func))((klass),(mid),(func),(arity));
                                                                                                                                        ^~~~~~
/opt/local/include/ruby-2.7.0/ruby/intern.h:1195:1: note: passing argument to parameter 'func' here
RB_METHOD_DEFINITION_DECL(rb_define_singleton_method, (2,3), (VALUE klass, const char *name), (klass, name))
^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1073:42: note: expanded from macro 'RB_METHOD_DEFINITION_DECL'
RB_METHOD_DEFINITION_DECL_CXX_BEGIN(def) \
                                         ^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1069:5: note: expanded from macro '\
RB_METHOD_DEFINITION_DECL_1'
    RB_METHOD_DEFINITION_DECL_C(def,nonnull,defname,decl,vars,funcargs) \
    ^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1042:118: note: expanded from macro 'RB_METHOD_DEFINITION_DECL_C'
    __attribute__((__unused__,__weakref__(#def),__nonnull__ nonnull))static void defname(RB_UNWRAP_MACRO decl,VALUE(*func)funcargs,int arity);
                                                                                                                     ^
src/line_editor.c:1626:5: warning: incompatible function pointer types passing 'VALUE (VALUE, VALUE)' (aka 'unsigned long (unsigned long, unsigned long)') to parameter of type 'VALUE (*)(VALUE)' (aka 'unsigned long (*)(unsigned long)') [-Wincompatible-function-pointer-types]
    rb_define_singleton_method(mLineEditor, "completer_quote_characters",
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/local/include/ruby-2.7.0/ruby/intern.h:1218:137: note: expanded from macro 'rb_define_singleton_method'
#define rb_define_singleton_method(klass, mid, func, arity) rb_define_singleton_method_choose_prototypem3((arity),(func))((klass),(mid),(func),(arity));
                                                                                                                                        ^~~~~~
/opt/local/include/ruby-2.7.0/ruby/intern.h:1195:1: note: passing argument to parameter 'func' here
RB_METHOD_DEFINITION_DECL(rb_define_singleton_method, (2,3), (VALUE klass, const char *name), (klass, name))
^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1073:42: note: expanded from macro 'RB_METHOD_DEFINITION_DECL'
RB_METHOD_DEFINITION_DECL_CXX_BEGIN(def) \
                                         ^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1069:5: note: expanded from macro '\
RB_METHOD_DEFINITION_DECL_1'
    RB_METHOD_DEFINITION_DECL_C(def,nonnull,defname,decl,vars,funcargs) \
    ^
/opt/local/include/ruby-2.7.0/ruby/intern.h:1042:118: note: expanded from macro 'RB_METHOD_DEFINITION_DECL_C'
    __attribute__((__unused__,__weakref__(#def),__nonnull__ nonnull))static void defname(RB_UNWRAP_MACRO decl,VALUE(*func)funcargs,int arity);
                                                                                                                     ^
2 warnings generated.
linking shared-object gitsh/line_editor_native.bundle
ld: warning: dylib (/opt/local/lib/libruby.2.7.dylib) was built for newer macOS version (11.2) than being linked (11.0)

Nice to see you too!

apt-key has been been deprecated and is scheduled for full removal in 2022.

Remove this command in favor of the preferred method of adding public key directly into the trusted.gpg.d folder.

source: https://salsa.debian.org/apt-team/apt/-/merge_requests/119

I meant it in the way of almost no commits, lots of issues open without responses on them - just asking though

Like the title says Is this project dead? - there seems to be no commits since 2019...

It depends what you mean by “dead.”

It's a tool that a lot of people use every day and find useful, myself included.

There are features that I'd like to add, but nothing huge. If there's a specific feature that you think is missing, then pull requests are welcome.

Could you post a bit more information? The output of the following commands from your regular shell would be useful:

echo $PATH
type npm
which -a npm

Like the title says Is this project dead? - there seems to be no commits since 2019...

Is there any way to get hooks, calling executables, to work?

For example, I've got a VueJs project setup with the npm run lint hook, to lint the files before push - but gitsh will fail as it cannot find npm

Is there a way to unlink and leave the dot files as file instead of symlink?

I guess I'm looking for the opposite of mkrc which takes ~/.vimrc and changes to a symlink to ~/.dotfiles/vimrc. Using rcdn vimrc will delete the symlink which is not what I want. What I'd like to to be able to run mkrc in reverse so it effectively reverses the action, removing it from RCM and replacing the symlinked version with the original dotfile.

Is that possible?

That's perfect. Thank you!

Hello, here is a workaround:

cd $HOME
# Erase link
rcdn vimrc
# Create the copy
rcup -C vimrc

Does it work for your case ?